Devices, methods, and systems for managing representations of entities through use of privacy beacons

ABSTRACT

Computationally implemented methods and systems include acquiring a block of encrypted data that corresponds to an image that has been encrypted through use of a unique device code associated with an image capture device configured to capture the image that includes a representation of a feature of an entity, obtaining a privacy metadata that corresponds to a detection of a privacy beacon in the image, said at least one image captured by the image capture device, said privacy beacon associated with the entity, and determining, at least partly based on the obtained privacy metadata, and partly based on a calculation related to the block of encrypted data that corresponds to the whether to allow one or more processes related to the encrypted data block. In addition to the foregoing, other aspects are described in the claims, drawings, and text.

CROSS-REFERENCE TO RELATED APPLICATIONS

If an Application Data Sheet (ADS) has been filed on the filing date ofthis application, it is incorporated by reference herein. Anyapplications claimed on the ADS for priority under 35 U.S.C. §§ 119,120, 121, or 365(c), and any and all parent, grandparent,great-grandparent, etc. applications of such applications, are alsoincorporated by reference, including any priority claims made in thoseapplications and any material incorporated by reference, to the extentsuch subject matter is not inconsistent herewith.

The present application is related to and/or claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Priority Applications”), if any, listed below(e.g., claims earliest available priority dates for other thanprovisional patent applications or claims benefits under 35 USC § 119(e)for provisional patent applications, for any and all parent,grandparent, great-grandparent, etc. applications of the PriorityApplication(s)). In addition, the present application is related to the“Related Applications,” if any, listed below.

PRIORITY APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation of U.S. patent application Ser.No. 14/148,523, entitled DEVICES, METHODS, AND SYSTEMS FOR MANAGINGREPRESENTATIONS OF ENTITIES THROUGH USE OF PRIVACY BEACONS, namingPablos Holman, Roderick A. Hyde, Royce A. Levien, Richard T. Lord,Robert W. Lord, and Mark A. Malamud as inventors, filed 6 Jan. 2014,which is currently co-pending or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/051,213, entitled METHODS, SYSTEMS, AND DEVICESFOR FACILITATING VIABLE DISTRIBUTION OF DATA COLLECTED BY WEARABLECOMPUTATION, naming Pablos Holman, Roderick A. Hyde, Royce A. Levien,Richard T. Lord, Robert W. Lord, and Mark A. Malamud as inventors, filed10 Oct. 2013, which is currently co-pending or is an application ofwhich a currently co-pending application is entitled to the benefit ofthe filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/055,471, entitled METHODS, SYSTEMS, AND DEVICESFOR HANDLING IMAGE DATA FROM CAPTURED IMAGES, naming Pablos Holman,Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, andMark A. Malamud as inventors, filed 16 Oct. 2013, which is currentlyco-pending or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/055,543, entitled METHODS, SYSTEMS, AND DEVICESFOR HANDLING IMAGE DATA FROM CAPTURED IMAGES, naming Pablos Holman,Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, andMark A. Malamud as inventors, filed 16 Oct. 2013, which is currentlyco-pending or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/084,254, entitled DEVICES, METHODS, AND SYSTEMSFOR ANALYZING CAPTURED IMAGE DATA AND PRIVACY DATA, naming PablosHolman, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W.Lord, and Mark A. Malamud as inventors, filed 19 Nov. 2013, which iscurrently co-pending or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/084,579 entitled DEVICES, METHODS, AND SYSTEMSFOR ANALYZING CAPTURED IMAGE DATA AND PRIVACY DATA, naming PablosHolman, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W.Lord, and Mark A. Malamud as inventors, filed 19 Nov. 2013, which iscurrently co-pending or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/084,581, entitled METHODS, SYSTEMS, AND DEVICESFOR HANDLING IMAGE DATA FROM CAPTURED IMAGES, naming Pablos Holman,Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, andMark A. Malamud as inventors, filed 19 Nov. 2013, which is currentlyco-pending or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/084,591, entitled METHODS, SYSTEMS, AND DEVICESFOR HANDLING IMAGE DATA FROM CAPTURED IMAGES, naming Pablos Holman,Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, andMark A. Malamud as inventors, filed 19 Nov. 2013, which is currentlyco-pending or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/108,077, entitled METHODS, SYSTEMS, AND DEVICESFOR DELIVERING IMAGE DATA FROM CAPTURED IMAGES TO DEVICES, naming PablosHolman, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W.Lord, and Mark A. Malamud as inventors, filed 16 Dec. 2013, which iscurrently co-pending or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/108,107, entitled METHODS, SYSTEMS, AND DEVICESFOR DELIVERING IMAGE DATA FROM CAPTURED IMAGES TO DEVICES, naming PablosHolman, Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W.Lord, and Mark A. Malamud as inventors, filed 16 Dec. 2013, which iscurrently co-pending or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/108,185, entitled METHODS, SYSTEMS, AND DEVICESFOR HANDLING INSERTED DATA INTO CAPTURED IMAGES, naming Pablos Holman,Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, andMark A. Malamud as inventors, filed 16 Dec. 2013, which is currentlyco-pending or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/108,217, entitled METHODS, SYSTEMS, AND DEVICESFOR HANDLING INSERTED DATA INTO CAPTURED IMAGES, naming Pablos Holman,Roderick A. Hyde, Royce A. Levien, Richard T. Lord, Robert W. Lord, andMark A. Malamud as inventors, filed 16 Dec. 2013, which is currentlyco-pending or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/109,682, entitled METHODS, SYSTEMS, AND DEVICESFOR HANDLING CAPTURED IMAGE DATA THAT IS RECEIVED BY DEVICES, namingPablos Holman, Roderick A. Hyde, Royce A. Levien, Richard T. Lord,Robert W. Lord, and Mark A. Malamud as inventors, filed 17 Dec. 2013,which is currently co-pending or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/109,726, entitled METHODS, SYSTEMS, AND DEVICESFOR HANDLING CAPTURED IMAGE DATA THAT IS RECEIVED BY DEVICES, namingPablos Holman, Roderick A. Hyde, Royce A. Levien, Richard T. Lord,Robert W. Lord, and Mark A. Malamud as inventors, filed 17 Dec. 2013,which is currently co-pending or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/145,873, entitled METHODS, SYSTEMS, AND DEVICESFOR MONITORING PRIVACY BEACONS RELATED TO ENTITIES DEPICTED IN IMAGES,naming Pablos Holman, Roderick A. Hyde, Royce A. Levien, Richard T.Lord, Robert W. Lord, and Mark A. Malamud as inventors, filed 31 Dec.2013, which is currently co-pending or is an application of which acurrently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 14/145,886, entitled METHODS, SYSTEMS, AND DEVICESFOR MONITORING PRIVACY BEACONS RELATED TO ENTITIES DEPICTED IN IMAGES,naming Pablos Holman, Roderick A. Hyde, Royce A. Levien, Richard T.Lord, Robert W. Lord, and Mark A. Malamud as inventors, filed 31 Dec.2013, which is currently co-pending or is an application of which acurrently co-pending application is entitled to the benefit of thefiling date.

RELATED APPLICATIONS

None.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation, continuation-in-part, or divisional of a parentapplication. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOOfficial Gazette Mar. 18, 2003. The USPTO further has provided forms forthe Application Data Sheet which allow automatic loading ofbibliographic data but which require identification of each applicationas a continuation, continuation-in-part, or divisional of a parentapplication. The present Applicant Entity (hereinafter “Applicant”) hasprovided above a specific reference to the application(s) from whichpriority is being claimed as recited by statute. Applicant understandsthat the statute is unambiguous in its specific reference language anddoes not require either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant has provided designation(s) of arelationship between the present application and its parentapplication(s) as set forth above and in any ADS filed in thisapplication, but expressly points out that such designation(s) are notto be construed in any way as any type of commentary and/or admission asto whether or not the present application contains any new matter inaddition to the matter of its parent application(s).

If the listings of applications provided above are inconsistent with thelistings provided via an ADS, it is the intent of the Applicant to claimpriority to each application that appears in the Priority Applicationssection of the ADS and to each application that appears in the PriorityApplications section of this application.

All subject matter of the Priority Applications and the RelatedApplications and of any and all parent, grandparent, great-grandparent,etc. applications of the Priority Applications and the RelatedApplications, including any priority claims, is incorporated herein byreference to the extent such subject matter is not inconsistentherewith.

BACKGROUND

This application is related to the handling of the capture of imagesthat may include personality rights.

SUMMARY

Recently, there has been an increased popularity in wearable computers,e.g., computers that are placed in articles of clothing or clothingaccessories, e.g., watches, eyeglasses, shoes, jewelry, accessories,shirts, pants, headbands, and the like. As technology allows electronicdevices to become smaller and smaller, more and more items may be“smart” items, e.g., may contain a computer.

In addition, image capturing technology has also improved, allowing forhigh quality digital cameras that can capture pictures, audio, video, ora combination thereof. These digital cameras may be small enough to fitonto wearable computers, e.g., inside of eyeglasses. In some instances,the digital camera may blend into the eyeglasses mold, and may not beimmediately recognizable as a camera. Such eyeglasses may beindistinguishable or somewhat distinguishable from standard eyeglassesthat do not contain a camera and/or a computer.

Further, the cost of data storage has decreased dramatically, and it isnot uncommon for an average person in a developed nation to have accessto enough digital storage to store months' and/or years' worth of videoand pictures. As the cost of data storage has decreased dramatically, sotoo has the cost of processors to process that data, meaning thatautomation may be able to take an entire day's worth of surreptitiousrecording, and isolate those portions of the recording that capturedpersons, either specific persons or persons in general.

Accordingly, with technology, it is possible for a person to “wear” acomputer, in the form of eyeglasses, watches, shirts, hats, or through apocket-sized device carried by a person, e.g., a cellular telephonedevice. This wearable computer may be used to record people, e.g., tocapture pictures, audio, video, or a combination thereof a person,without their knowledge. Thus, conversations that a person may assume tobe private, may be recorded and widely distributed. Moreover, a personmay be surreptitiously recorded while they are in a locker room, in abathroom, or in a telephone booth. It may be difficult or impossible totell when a person is being recorded. Further, once proliferation ofthese wearable computers with digital cameras becomes widespread, peoplemust assume that they are under surveillance 100% of the time that theyare not in their house.

Therefore, a need has arisen to provide systems that attempt to limitthe capture and distribution of a person's personality rights. Thepresent invention is directed to devices, methods, and systems thatattempt to limit the capture and distribution of captured images ofpersons. Specifically, the present invention is directed to devices,methods, and systems that attempt to limit the capture and distributionof captured images of persons, implemented at a device that carries outthe capturing of the image. In some embodiments, this device may be awearable computer, but in other embodiments, any image capturing deviceor any device that has an image capturing device incorporated into itsfunctionality may implement the devices, methods, and systems describedherein.

In various embodiments, devices, methods, and systems may have acapability to capture images, and in which the capture of those imagesmay include capturing images of a person, persons, or portion(s) of aperson for which a privacy beacon may be associated. The privacy beaconmay be optical, digital, or other form (e.g., radio, electromagnetic,biomechanic, quantum-state, and the like), and may be detected throughdigital or optical operations, as discussed herein.

The instant application is directed at least in part to, but not limitedby, devices, methods, and systems that acquire a captured encryptedimage, and that acquire beacon data, and that make a determination atleast partly based on data that is acquired and that is related to oneor more of the captured image and the privacy beacon, whether directlyor indirectly, e.g., inferentially or tangentially.

In one or more various aspects, a method includes but is not limited toacquiring data that regards at least one feature of an entity that isdesignated for coverage by one or more terms of service, associating theone or more terms of service with a privacy beacon configured to bedetected in an image when the at least one feature of the entity iscaptured in the image, and providing the terms of service to a captureentity associated with a device that captured a captured image thatincludes the privacy beacon, in response to an indication that theprivacy beacon has been detected. In addition to the foregoing, othermethod aspects are described in the claims, drawings, and text forming apart of the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for affecting the herein-referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein-referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

In one or more various aspects, a system includes, but is not limitedto, means for acquiring data that regards at least one feature of anentity that is designated for coverage by one or more terms of service,means for associating the one or more terms of service with a privacybeacon configured to be detected in an image when the at least onefeature of the entity is captured in the image, and means for providingthe terms of service to a capture entity associated with a device thatcaptured a captured image that includes the privacy beacon, in responseto an indication that the privacy beacon has been detected. In additionto the foregoing, other system aspects are described in the claims,drawings, and text forming a part of the disclosure set forth herein.

In one or more various aspects, a system includes, but is not limitedto, circuitry for acquiring data that regards at least one feature of anentity that is designated for coverage by one or more terms of service,circuitry for associating the one or more terms of service with aprivacy beacon configured to be detected in an image when the at leastone feature of the entity is captured in the image, and circuitry forproviding the terms of service to a capture entity associated with adevice that captured a captured image that includes the privacy beacon,in response to an indication that the privacy beacon has been detected.In addition to the foregoing, other system aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one or more various aspects, a computer program product, comprising asignal bearing medium, bearing one or more instructions including, butnot limited to, one or more instructions for acquiring data that regardsat least one feature of an entity that is designated for coverage by oneor more terms of service, one or more instructions for associating theone or more terms of service with a privacy beacon configured to bedetected in an image when the at least one feature of the entity iscaptured in the image, and one or more instructions for providing theterms of service to a capture entity associated with a device thatcaptured a captured image that includes the privacy beacon, in responseto an indication that the privacy beacon has been detected. In additionto the foregoing, other computer program product aspects are describedin the claims, drawings, and text forming a part of the disclosure setforth herein.

In one or more various aspects, a device is defined by a computationallanguage, such that the device comprises one or more interchainedphysical machines ordered for acquiring data that regards at least onefeature of an entity that is designated for coverage by one or moreterms of service, one or more interchained physical machines ordered forassociating the one or more terms of service with a privacy beaconconfigured to be detected in an image when the at least one feature ofthe entity is captured in the image, and one or more interchainedphysical machines ordered for providing the terms of service to acapture entity associated with a device that captured a captured imagethat includes the privacy beacon, in response to an indication that theprivacy beacon has been detected.

In addition to the foregoing, various other method and/or system and/orprogram product aspects are set forth and described in the teachingssuch as text (e.g., claims and/or detailed description) and/or drawingsof the present disclosure.

The foregoing is a summary and thus may contain simplifications,generalizations, inclusions, and/or omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is NOT intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent by referenceto the detailed description, the corresponding drawings, and/or in theteachings set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

For a more complete understanding of embodiments, reference now is madeto the following descriptions taken in connection with the accompanyingdrawings. The use of the same symbols in different drawings typicallyindicates similar or identical items, unless context dictates otherwise.The illustrative embodiments described in the detailed description,drawings, and claims are not meant to be limiting. Other embodiments maybe utilized, and other changes may be made, without departing from thespirit or scope of the subject matter presented here.

FIG. 1, including FIGS. 1-A through 1-T, shows a high-level systemdiagram of one or more exemplary environments in which transactions andpotential transactions may be carried out, according to one or moreembodiments. FIG. 1 forms a partially schematic diagram of anenvironment(s) and/or an implementation(s) of technologies describedherein when FIGS. 1-A through 1-T are stitched together in the mannershown in FIG. 1-P, which is reproduced below in table format.

In accordance with 37 C.F.R. § 1.84(h)(2), FIG. 1 shows “a view of alarge machine or device in its entirety . . . broken into partial views. . . extended over several sheets” labeled FIG. 1-A through FIG. 1-T(Sheets 1-20). The “views on two or more sheets form, in effect, asingle complete view, [and] the views on the several sheets . . . [are]so arranged that the complete figure can be assembled” from “partialviews drawn on separate sheets . . . linked edge to edge. Thus, in FIG.1, the partial view FIGS. 1-A through 1-T are ordered alphabetically, byincreasing in columns from left to right, and increasing in rows top tobottom, as shown in the following table:

TABLE 1 Table showing alignment of enclosed drawings to form partialschematic of one or more environments. (1, 1) - FIG. 1-A (1, 2) - FIG.1-B (1, 3) - FIG. 1-C (1, 4) - FIG. 1-D (1, 5) - FIG. 1-E (2, 1) - FIG.1-F (2, 2) - FIG. 1-G (2, 3) - FIG. 1-H (2, 4) - FIG. 1-I (2, 5) - FIG.1-J (3, 1) - FIG. 1-K (3, 2) - FIG. 1-L (3, 3) - FIG. 1-M (3, 4) - FIG.1-N (3, 5) - FIG. 1-O (4, 1) - FIG. 1-P (4, 2) - FIG. 1-Q (4, 3) - FIG.1-R (4, 4) - FIG. 1-S (4, 5) - FIG. 1-T

In accordance with 37 C.F.R. § 1.84(h)(2), FIG. 1 is “ . . . a view of alarge machine or device in its entirety . . . broken into partial views. . . extended over several sheets . . . [with] no loss in facility ofunderstanding the view.” The partial views drawn on the several sheetsindicated in the above table are capable of being linked edge to edge,so that no partial view contains parts of another partial view. As here,“where views on two or more sheets form, in effect, a single completeview, the views on the several sheets are so arranged that the completefigure can be assembled without concealing any part of any of the viewsappearing on the various sheets.” 37 C.F.R. § 1.84(h)(2).

It is noted that one or more of the partial views of the drawings may beblank, or may not contain substantive elements (e.g., may show onlylines, connectors, and the like). These drawings are included in orderto assist readers of the application in assembling the single completeview from the partial sheet format required for submission by the USPTO,and, while their inclusion is not required and may be omitted in this orother applications, their inclusion is proper, and should be consideredintentional.

FIG. 1-A, when placed at position (1,1), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-B, when placed at position (1,2), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-C, when placed at position (1,3), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-D, when placed at position (1,4), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-E, when placed at position (1,5), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-F, when placed at position (2,1), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-G, when placed at position (2,2), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-H, when placed at position (2,3), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-I, when placed at position (2,4), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-J, when placed at position (2,5), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-K, when placed at position (3,1), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-L, when placed at position (3,2), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-M, when placed at position (3,3), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-N, when placed at position (3,4), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-O, when placed at position (3,5), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-P, when placed at position (4,1), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-Q, when placed at position (4,2), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-R, when placed at position (4,3), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-S, when placed at position (4,4), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 1-T, when placed at position (4,5), forms at least a portion of apartially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein.

FIG. 2A shows a high-level block diagram of an exemplary environment200, according to one or more embodiments.

FIG. 2B shows a high-level block diagram of a computing device, e.g., abeacon management device 260 operating in an exemplary environment 200,according to one or more embodiments.

FIG. 3A shows a high-level block diagram of an exemplary image capturedevice 302, according to one or more embodiments.

FIG. 3B shows a high-level block diagram of an exemplary image capturedevice 304, according to one or more embodiments.

FIG. 3C shows a high-level block diagram of an exemplary image capturedevice 306, according to one or more embodiments.

FIG. 3D shows a high-level block diagram of an exemplary image capturedevice 308, according to one or more embodiments.

FIG. 3E shows a high-level block diagram of an exemplary image capturedevice 309, according to one or more embodiments.

FIG. 4A shows a high-level block diagram of an exemplary environment400A including a computing device 420A and a server device 430A.

FIG. 4B shows a high-level block diagram of an exemplary environment400B including a computing device 420B and a server device 430B.

FIG. 4C shows a high-level block diagram of an exemplary environment400C including a computing device 420C and a server device 430C.

FIG. 4D shows a high-level block diagram of an exemplary environment400D including a computing device 420D and a server device 430D.

FIG. 4E shows a high-level block diagram of an exemplary environment400E including a computing device 420E and a server device 430E.

FIG. 5A shows a high-level block diagram of an exemplary environment500A including a computing device 520A and a server device 530A.

FIG. 5B shows a high-level block diagram of an exemplary environment500B including a computing device 520B and a server device 530B.

FIG. 5C shows a high-level block diagram of an exemplary environment500C including a computing device 520C and a server device 530C.

FIG. 5D shows a high-level block diagram of an exemplary environment500D including a computing device 520D and a server device 530D.

FIG. 6, including FIGS. 6A-6C, shows a particular perspective of anentity data that is related to at least one feature of an entity that isconfigured to be assigned for coverage by one or more terms of serviceobtaining module 252 of processing module 250 of beacon managementdevice 260 of FIG. 2B, according to an embodiment.

FIG. 7, including FIGS. 7A-7F, shows a particular perspective of anassociation of the one or more terms of service with a privacy beaconthat is configured to be detected when the at least one feature of theentity is captured in a captured image facilitating module 254 ofprocessing module 250 of beacon management device 260 of FIG. 2B,according to an embodiment.

FIG. 8, including FIGS. 8A-8D, shows a particular perspective of anassociated one or more terms of service providing to a capture entityassociated with a device that possesses the captured image in responseto an indication that the privacy beacon has been detected module 256 ofprocessing module 250 of beacon management device 260 of FIG. 2B,according to an embodiment.

FIG. 9 is a high-level logic flowchart of a process, e.g., operationalflow 900, according to an embodiment.

FIG. 10A is a high-level logic flow chart of a process depictingalternate implementations of an acquiring data that regards at least onefeature of an entity operation 902, according to one or moreembodiments.

FIG. 10B is a high-level logic flow chart of a process depictingalternate implementations of an acquiring data that regards at least onefeature of an entity operation 902, according to one or moreembodiments.

FIG. 10C is a high-level logic flow chart of a process depictingalternate implementations of an acquiring data that regards at least onefeature of an entity operation 902, according to one or moreembodiments.

FIG. 11A is a high-level logic flow chart of a process depictingalternate implementations of an associating the one or more terms ofservice with a privacy beacon 904, according to one or more embodiments.

FIG. 11B is a high-level logic flow chart of a process depictingalternate implementations of an associating the one or more terms ofservice with a privacy beacon 904, according to one or more embodiments.

FIG. 11C is a high-level logic flow chart of a process depictingalternate implementations of an associating the one or more terms ofservice with a privacy beacon 904, according to one or more embodiments.

FIG. 11D is a high-level logic flow chart of a process depictingalternate implementations of an associating the one or more terms ofservice with a privacy beacon 904, according to one or more embodiments.

FIG. 11E is a high-level logic flow chart of a process depictingalternate implementations of an associating the one or more terms ofservice with a privacy beacon 904, according to one or more embodiments.

FIG. 11F is a high-level logic flow chart of a process depictingalternate implementations of an associating the one or more terms ofservice with a privacy beacon 904, according to one or more embodiments.

FIG. 12A is a high-level logic flow chart of a process depictingalternate implementations of a providing the terms of service to acapture entity operation 906, according to one or more embodiments.

FIG. 12B is a high-level logic flow chart of a process depictingalternate implementations of a providing the terms of service to acapture entity operation 906, according to one or more embodiments.

FIG. 12C is a high-level logic flow chart of a process depictingalternate implementations of a providing the terms of service to acapture entity operation 906, according to one or more embodiments.

FIG. 12D is a high-level logic flow chart of a process depictingalternate implementations of a providing the terms of service to acapture entity operation 906, according to one or more embodiments.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar or identical components oritems, unless context dictates otherwise. The illustrative embodimentsdescribed in the detailed description, drawings, and claims are notmeant to be limiting. Other embodiments may be utilized, and otherchanges may be made, without departing from the spirit or scope of thesubject matter presented here.

Thus, in accordance with various embodiments, computationallyimplemented methods, systems, circuitry, articles of manufacture,ordered chains of matter, and computer program products are designed to,among other things, provide an interface for acquiring data that regardsat least one feature of an entity that is designated for coverage by oneor more terms of service, associating the one or more terms of servicewith a privacy beacon configured to be detected in an image when the atleast one feature of the entity is captured in the image, and providingthe terms of service to a capture entity associated with a device thatcaptured a captured image that includes the privacy beacon, in responseto an indication that the privacy beacon has been detected.

The claims, description, and drawings of this application may describeone or more of the instant technologies in operational/functionallanguage, for example as a set of operations to be performed by acomputer. Such operational/functional description in most instanceswould be understood by one skilled the art as specifically-configuredhardware (e.g., because a general purpose computer in effect becomes aspecial purpose computer once it is programmed to perform particularfunctions pursuant to instructions from program software).

Importantly, although the operational/functional descriptions describedherein are understandable by the human mind, they are not abstract ideasof the operations/functions divorced from computational implementationof those operations/functions. Rather, the operations/functionsrepresent a specification for the massively complex computationalmachines or other means. As discussed in detail below, theoperational/functional language must be read in its proper technologicalcontext, i.e., as concrete specifications for physical implementations.

The logical operations/functions described herein are a distillation ofmachine specifications or other physical mechanisms specified by theoperations/functions such that the otherwise inscrutable machinespecifications may be comprehensible to the human mind. The distillationalso allows one of skill in the art to adapt the operational/functionaldescription of the technology across many different specific vendors'hardware configurations or platforms, without being limited to specificvendors' hardware configurations or platforms.

Some of the present technical description (e.g., detailed description,drawings, claims, etc.) may be set forth in terms of logicaloperations/functions. As described in more detail in the followingparagraphs, these logical operations/functions are not representationsof abstract ideas, but rather representative of static or sequencedspecifications of various hardware elements. Differently stated, unlesscontext dictates otherwise, the logical operations/functions will beunderstood by those of skill in the art to be representative of staticor sequenced specifications of various hardware elements. This is truebecause tools available to one of skill in the art to implementtechnical disclosures set forth in operational/functional formats—toolsin the form of a high-level programming language (e.g., C, java, visualbasic, etc.), or tools in the form of Very high speed HardwareDescription Language (“VHDL,” which is a language that uses text todescribe logic circuits)—are generators of static or sequencedspecifications of various hardware configurations. This fact issometimes obscured by the broad term “software,” but, as shown by thefollowing explanation, those skilled in the art understand that what istermed “software” is a shorthand for a massively complexinterchaining/specification of ordered-matter elements. The term“ordered-matter elements” may refer to physical components ofcomputation, such as assemblies of electronic logic gates, molecularcomputing logic constituents, quantum computing mechanisms, etc.

For example, a high-level programming language is a programming languagewith strong abstraction, e.g., multiple levels of abstraction, from thedetails of the sequential organizations, states, inputs, outputs, etc.,of the machines that a high-level programming language actuallyspecifies. See, e.g., Wikipedia, High-level programming language,http://en.wikipedia.org/wiki/High-level_programming_language (as of Jun.5, 2012, 21:00 GMT). In order to facilitate human comprehension, in manyinstances, high-level programming languages resemble or even sharesymbols with natural languages. See, e.g., Wikipedia, Natural language,http://en.wikipedia.org/wiki/Natural_language (as of Jun. 5, 2012, 21:00GMT).

It has been argued that because high-level programming languages usestrong abstraction (e.g., that they may resemble or share symbols withnatural languages), they are therefore a “purely mental construct”(e.g., that “software”—a computer program or computer programming—issomehow an ineffable mental construct, because at a high level ofabstraction, it can be conceived and understood in the human mind). Thisargument has been used to characterize technical description in the formof functions/operations as somehow “abstract ideas.” In fact, intechnological arts (e.g., the information and communicationtechnologies) this is not true.

The fact that high-level programming languages use strong abstraction tofacilitate human understanding should not be taken as an indication thatwhat is expressed is an abstract idea. In fact, those skilled in the artunderstand that just the opposite is true. If a high-level programminglanguage is the tool used to implement a technical disclosure in theform of functions/operations, those skilled in the art will recognizethat, far from being abstract, imprecise, “fuzzy,” or “mental” in anysignificant semantic sense, such a tool is instead a nearincomprehensibly precise sequential specification of specificcomputational machines—the parts of which are built up byactivating/selecting such parts from typically more generalcomputational machines over time (e.g., clocked time). This fact issometimes obscured by the superficial similarities between high-levelprogramming languages and natural languages. These superficialsimilarities also may cause a glossing over of the fact that high-levelprogramming language implementations ultimately perform valuable work bycreating/controlling many different computational machines.

The many different computational machines that a high-level programminglanguage specifies are almost unimaginably complex. At base, thehardware used in the computational machines typically consists of sometype of ordered matter (e.g., traditional electronic devices (e.g.,transistors), deoxyribonucleic acid (DNA), quantum devices, mechanicalswitches, optics, fluidics, pneumatics, optical devices (e.g., opticalinterference devices, molecules, etc.) that are arranged to form logicgates. Logic gates are typically physical devices that may beelectrically, mechanically, chemically, or otherwise driven to changephysical state in order to create a physical reality of Boolean logic.

Logic gates may be arranged to form logic circuits, which are typicallyphysical devices that may be electrically, mechanically, chemically, orotherwise driven to create a physical reality of certain logicalfunctions. Types of logic circuits include such devices as multiplexers,registers, arithmetic logic units (ALUs), computer memory, etc., eachtype of which may be combined to form yet other types of physicaldevices, such as a central processing unit (CPU)—the best known of whichis the microprocessor. A modern microprocessor will often contain morethan one hundred million logic gates in its many logic circuits (andoften more than a billion transistors). See, e.g., Wikipedia, Logicgates, http://en.wikipedia.org/wiki/Logic_gates (as of Jun. 5, 2012,21:03 GMT).

The logic circuits forming the microprocessor are arranged to provide amicroarchitecture that will carry out the instructions defined by thatmicroprocessor's defined Instruction Set Architecture. The InstructionSet Architecture is the part of the microprocessor architecture relatedto programming, including the native data types, instructions,registers, addressing modes, memory architecture, interrupt andexception handling, and external Input/Output. See, e.g., Wikipedia,Computer architecture,http://en.wikipedia.org/wiki/Computer_architecture (as of Jun. 5, 2012,21:03 GMT).

The Instruction Set Architecture includes a specification of the machinelanguage that can be used by programmers to use/control themicroprocessor. Since the machine language instructions are such thatthey may be executed directly by the microprocessor, typically theyconsist of strings of binary digits, or bits. For example, a typicalmachine language instruction might be many bits long (e.g., 32, 64, or128 bit strings are currently common). A typical machine languageinstruction might take the form “11110000101011110000111100111111” (a 32bit instruction).

It is significant here that, although the machine language instructionsare written as sequences of binary digits, in actuality those binarydigits specify physical reality. For example, if certain semiconductorsare used to make the operations of Boolean logic a physical reality, theapparently mathematical bits “1” and “0” in a machine languageinstruction actually constitute shorthand that specifies the applicationof specific voltages to specific wires. For example, in somesemiconductor technologies, the binary number “1” (e.g., logical “1”) ina machine language instruction specifies around +5 volts applied to aspecific “wire” (e.g., metallic traces on a printed circuit board) andthe binary number “0” (e.g., logical “0”) in a machine languageinstruction specifies around −5 volts applied to a specific “wire.” Inaddition to specifying voltages of the machines' configuration, suchmachine language instructions also select out and activate specificgroupings of logic gates from the millions of logic gates of the moregeneral machine. Thus, far from abstract mathematical expressions,machine language instruction programs, even though written as a stringof zeros and ones, specify many, many constructed physical machines orphysical machine states.

Machine language is typically incomprehensible by most humans (e.g., theabove example was just ONE instruction, and some personal computersexecute more than two billion instructions every second). See, e.g.,Wikipedia, Instructions per second,http://en.wikipedia.org/wiki/Instructions_per_second (as of Jun. 5,2012, 21:04 GMT). Thus, programs written in machine language—which maybe tens of millions of machine language instructions long—areincomprehensible. In view of this, early assembly languages weredeveloped that used mnemonic codes to refer to machine languageinstructions, rather than using the machine language instructions'numeric values directly (e.g., for performing a multiplicationoperation, programmers coded the abbreviation “mult,” which representsthe binary number “011000” in MIPS machine code). While assemblylanguages were initially a great aid to humans controlling themicroprocessors to perform work, in time the complexity of the work thatneeded to be done by the humans outstripped the ability of humans tocontrol the microprocessors using merely assembly languages.

At this point, it was noted that the same tasks needed to be done overand over, and the machine language necessary to do those repetitivetasks was the same. In view of this, compilers were created. A compileris a device that takes a statement that is more comprehensible to ahuman than either machine or assembly language, such as “add 2+2 andoutput the result,” and translates that human understandable statementinto a complicated, tedious, and immense machine language code (e.g.,millions of 32, 64, or 128 bit length strings). Compilers thus translatehigh-level programming language into machine language.

This compiled machine language, as described above, is then used as thetechnical specification which sequentially constructs and causes theinteroperation of many different computational machines such thathumanly useful, tangible, and concrete work is done. For example, asindicated above, such machine language—the compiled version of thehigher-level language—functions as a technical specification whichselects out hardware logic gates, specifies voltage levels, voltagetransition timings, etc., such that the humanly useful work isaccomplished by the hardware.

Thus, a functional/operational technical description, when viewed by oneof skill in the art, is far from an abstract idea. Rather, such afunctional/operational technical description, when understood throughthe tools available in the art such as those just described, is insteadunderstood to be a humanly understandable representation of a hardwarespecification, the complexity and specificity of which far exceeds thecomprehension of most any one human. With this in mind, those skilled inthe art will understand that any such operational/functional technicaldescriptions—in view of the disclosures herein and the knowledge ofthose skilled in the art—may be understood as operations made intophysical reality by (a) one or more interchained physical machines, (b)interchained logic gates configured to create one or more physicalmachine(s) representative of sequential/combinatorial logic(s), (c)interchained ordered matter making up logic gates (e.g., interchainedelectronic devices (e.g., transistors), DNA, quantum devices, mechanicalswitches, optics, fluidics, pneumatics, molecules, etc.) that createphysical reality representative of logic(s), or (d) virtually anycombination of the foregoing. Indeed, any physical object which has astable, measurable, and changeable state may be used to construct amachine based on the above technical description. Charles Babbage, forexample, constructed the first computer out of wood and powered bycranking a handle.

Thus, far from being understood as an abstract idea, those skilled inthe art will recognize a functional/operational technical description asa humanly-understandable representation of one or more almostunimaginably complex and time sequenced hardware instantiations. Thefact that functional/operational technical descriptions might lendthemselves readily to high-level computing languages (or high-levelblock diagrams for that matter) that share some words, structures,phrases, etc. with natural language simply cannot be taken as anindication that such functional/operational technical descriptions areabstract ideas, or mere expressions of abstract ideas. In fact, asoutlined herein, in the technological arts this is simply not true. Whenviewed through the tools available to those of skill in the art, suchfunctional/operational technical descriptions are seen as specifyinghardware configurations of almost unimaginable complexity.

As outlined above, the reason for the use of functional/operationaltechnical descriptions is at least twofold. First, the use offunctional/operational technical descriptions allows near-infinitelycomplex machines and machine operations arising from interchainedhardware elements to be described in a manner that the human mind canprocess (e.g., by mimicking natural language and logical narrativeflow). Second, the use of functional/operational technical descriptionsassists the person of skill in the art in understanding the describedsubject matter by providing a description that is more or lessindependent of any specific vendor's piece(s) of hardware.

The use of functional/operational technical descriptions assists theperson of skill in the art in understanding the described subject mattersince, as is evident from the above discussion, one could easily,although not quickly, transcribe the technical descriptions set forth inthis document as trillions of ones and zeroes, billions of single linesof assembly-level machine code, millions of logic gates, thousands ofgate arrays, or any number of intermediate levels of abstractions.However, if any such low-level technical descriptions were to replacethe present technical description, a person of skill in the art couldencounter undue difficulty in implementing the disclosure, because sucha low-level technical description would likely add complexity without acorresponding benefit (e.g., by describing the subject matter utilizingthe conventions of one or more vendor-specific pieces of hardware).Thus, the use of functional/operational technical descriptions assiststhose of skill in the art by separating the technical descriptions fromthe conventions of any vendor-specific piece of hardware.

In view of the foregoing, the logical operations/functions set forth inthe present technical description are representative of static orsequenced specifications of various ordered-matter elements, in orderthat such specifications may be comprehensible to the human mind andadaptable to create many various hardware configurations. The logicaloperations/functions disclosed herein should be treated as such, andshould not be disparagingly characterized as abstract ideas merelybecause the specifications they represent are presented in a manner thatone of skill in the art can readily understand and apply in a mannerindependent of a specific vendor's hardware implementation.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software (e.g., a high-level computer program servingas a hardware specification), and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software (e.g., a high-level computer program serving as a hardwarespecification), and/or firmware), and that the preferred vehicle willvary with the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly software (e.g., ahigh-level computer program serving as a hardware specification)implementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software (e.g., a high-level computerprogram serving as a hardware specification), and/or firmware in one ormore machines, compositions of matter, and articles of manufacture,limited to patentable subject matter under 35 U.S.C. § 101. Hence, thereare several possible vehicles by which the processes and/or devicesand/or other technologies described herein may be effected, none ofwhich is inherently superior to the other in that any vehicle to beutilized is a choice dependent upon the context in which the vehiclewill be deployed and the specific concerns (e.g., speed, flexibility, orpredictability) of the implementer, any of which may vary. Those skilledin the art will recognize that optical aspects of implementations willtypically employ optically-oriented hardware, software (e.g., ahigh-level computer program serving as a hardware specification), and orfirmware.

In some implementations described herein, logic and similarimplementations may include computer programs or other controlstructures. Electronic circuitry, for example, may have one or morepaths of electrical current constructed and arranged to implementvarious functions as described herein. In some implementations, one ormore media may be configured to bear a device-detectable implementationwhen such media hold or transmit device detectable instructions operableto perform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware (e.g., a high-level computer program serving as a hardwarespecification) or firmware, or of gate arrays or programmable hardware,such as by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software (e.g., a high-level computerprogram serving as a hardware specification), firmware components,and/or general-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Alternatively or additionally, implementations may include executing aspecial-purpose instruction sequence or invoking circuitry for enabling,triggering, coordinating, requesting, or otherwise causing one or moreoccurrences of virtually any functional operation described herein. Insome variants, operational or other logical descriptions herein may beexpressed as source code and compiled or otherwise invoked as anexecutable instruction sequence. In some contexts, for example,implementations may be provided, in whole or in part, by source code,such as C++, or other code sequences. In other implementations, sourceor other code implementation, using commercially available and/ortechniques in the art, may be compiled/implemented/translated/convertedinto a high-level descriptor language (e.g., initially implementingdescribed technologies in C or C++ programming language and thereafterconverting the programming language implementation into alogic-synthesizable language implementation, a hardware descriptionlanguage implementation, a hardware design simulation implementation,and/or other such similar mode(s) of expression). For example, some orall of a logical expression (e.g., computer programming languageimplementation) may be manifested as a Verilog-type hardware description(e.g., via Hardware Description Language (HDL) and/or Very High SpeedIntegrated Circuit Hardware Descriptor Language (VHDL)) or othercircuitry model which may then be used to create a physicalimplementation having hardware (e.g., an Application Specific IntegratedCircuit). Those skilled in the art will recognize how to obtain,configure, and optimize suitable transmission or computational elements,material supplies, actuators, or other structures in light of theseteachings.

Those skilled in the art will recognize that it is common within the artto implement devices and/or processes and/or systems, and thereafter useengineering and/or other practices to integrate such implemented devicesand/or processes and/or systems into more comprehensive devices and/orprocesses and/or systems. That is, at least a portion of the devicesand/or processes and/or systems described herein can be integrated intoother devices and/or processes and/or systems via a reasonable amount ofexperimentation. Those having skill in the art will recognize thatexamples of such other devices and/or processes and/or systems mightinclude—as appropriate to context and application—all or part of devicesand/or processes and/or systems of (a) an air conveyance (e.g., anairplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., acar, truck, locomotive, tank, armored personnel carrier, etc.), (c) abuilding (e.g., a home, warehouse, office, etc.), (d) an appliance(e.g., a refrigerator, a washing machine, a dryer, etc.), (e) acommunications system (e.g., a networked system, a telephone system, aVoice over IP system, etc.), (f) a business entity (e.g., an InternetService Provider (ISP) entity such as Comcast Cable, Qwest, SouthwesternBell, etc.), or (g) a wired/wireless services entity (e.g., Sprint,Cingular, Nextel, etc.), etc.

In certain cases, use of a system or method may occur in a territoryeven if components are located outside the territory. For example, in adistributed computing context, use of a distributed computing system mayoccur in a territory even though parts of the system may be locatedoutside of the territory (e.g., relay, server, processor, signal-bearingmedium, transmitting computer, receiving computer, etc. located outsidethe territory).

A sale of a system or method may likewise occur in a territory even ifcomponents of the system or method are located and/or used outside theterritory. Further, implementation of at least part of a system forperforming a method in one territory does not preclude use of the systemin another territory

In a general sense, those skilled in the art will recognize that thevarious embodiments described herein can be implemented, individuallyand/or collectively, by various types of electro-mechanical systemshaving a wide range of electrical components such as hardware, software,firmware, and/or virtually any combination thereof, limited topatentable subject matter under 35 U.S.C. 101; and a wide range ofcomponents that may impart mechanical force or motion such as rigidbodies, spring or torsional bodies, hydraulics, electro-magneticallyactuated devices, and/or virtually any combination thereof.Consequently, as used herein “electro-mechanical system” includes, butis not limited to, electrical circuitry operably coupled with atransducer (e.g., an actuator, a motor, a piezoelectric crystal, a MicroElectro Mechanical System (MEMS), etc.), electrical circuitry having atleast one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of memory(e.g., random access, flash, read only, etc.)), electrical circuitryforming a communications device (e.g., a modem, communications switch,optical-electrical equipment, etc.), and/or any non-electrical analogthereto, such as optical or other analogs (e.g., graphene basedcircuitry). Those skilled in the art will also appreciate that examplesof electro-mechanical systems include but are not limited to a varietyof consumer electronics systems, medical devices, as well as othersystems such as motorized transport systems, factory automation systems,security systems, and/or communication/computing systems. Those skilledin the art will recognize that electro-mechanical as used herein is notnecessarily limited to a system that has both electrical and mechanicalactuation except as context may dictate otherwise.

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware,and/or any combination thereof can be viewed as being composed ofvarious types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configured by acomputer program (e.g., a general purpose computer configured by acomputer program which at least partially carries out processes and/ordevices described herein, or a microprocessor configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein), electrical circuitry forming a memory device (e.g.,forms of memory (e.g., random access, flash, read only, etc.)), and/orelectrical circuitry forming a communications device (e.g., a modem,communications switch, optical-electrical equipment, etc.). Those havingskill in the art will recognize that the subject matter described hereinmay be implemented in an analog or digital fashion or some combinationthereof.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into animage processing system. Those having skill in the art will recognizethat a typical image processing system generally includes one or more ofa system unit housing, a video display device, memory such as volatileor non-volatile memory, processors such as microprocessors or digitalsignal processors, computational entities such as operating systems,drivers, applications programs, one or more interaction devices (e.g., atouch pad, a touch screen, an antenna, etc.), control systems includingfeedback loops and control motors (e.g., feedback for sensing lensposition and/or velocity; control motors for moving/distorting lenses togive desired focuses). An image processing system may be implementedutilizing suitable commercially available components, such as thosetypically found in digital still systems and/or digital motion systems.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a dataprocessing system. Those having skill in the art will recognize that adata processing system generally includes one or more of a system unithousing, a video display device, memory such as volatile or non-volatilememory, processors such as microprocessors or digital signal processors,computational entities such as operating systems, drivers, graphicaluser interfaces, and applications programs, one or more interactiondevices (e.g., a touch pad, a touch screen, an antenna, etc.), and/orcontrol systems including feedback loops and control motors (e.g.,feedback for sensing position and/or velocity; control motors for movingand/or adjusting components and/or quantities). A data processing systemmay be implemented utilizing suitable commercially available components,such as those typically found in data computing/communication and/ornetwork computing/communication systems.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a motesystem. Those having skill in the art will recognize that a typical motesystem generally includes one or more memories such as volatile ornon-volatile memories, processors such as microprocessors or digitalsignal processors, computational entities such as operating systems,user interfaces, drivers, sensors, actuators, applications programs, oneor more interaction devices (e.g., an antenna USB ports, acoustic ports,etc.), control systems including feedback loops and control motors(e.g., feedback for sensing or estimating position and/or velocity;control motors for moving and/or adjusting components and/orquantities). A mote system may be implemented utilizing suitablecomponents, such as those found in mote computing/communication systems.Specific examples of such components entail such as Intel Corporation'sand/or Crossbow Corporation's mote components and supporting hardware,software, and/or firmware.

For the purposes of this application, “cloud” computing may beunderstood as described in the cloud computing literature. For example,cloud computing may be methods and/or systems for the delivery ofcomputational capacity and/or storage capacity as a service. The “cloud”may refer to one or more hardware and/or software components thatdeliver or assist in the delivery of computational and/or storagecapacity, including, but not limited to, one or more of a client, anapplication, a platform, an infrastructure, and/or a server The cloudmay refer to any of the hardware and/or software associated with aclient, an application, a platform, an infrastructure, and/or a server.For example, cloud and cloud computing may refer to one or more of acomputer, a processor, a storage medium, a router, a switch, a modem, avirtual machine (e.g., a virtual server), a data center, an operatingsystem, a middleware, a firmware, a hardware back-end, a softwareback-end, and/or a software application. A cloud may refer to a privatecloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloudmay be a shared pool of configurable computing resources, which may bepublic, private, semi-private, distributable, scaleable, flexible,temporary, virtual, and/or physical. A cloud or cloud service may bedelivered over one or more types of network, e.g., a mobilecommunication network, and the Internet.

As used in this application, a cloud or a cloud service may include oneor more of infrastructure-as-a-service (“IaaS”), platform-as-a-service(“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service(“DaaS”). As a non-exclusive example, IaaS may include, e.g., one ormore virtual server instantiations that may start, stop, access, and/orconfigure virtual servers and/or storage centers (e.g., providing one ormore processors, storage space, and/or network resources on-demand,e.g., EMC and Rackspace). PaaS may include, e.g., one or more softwareand/or development tools hosted on an infrastructure (e.g., a computingplatform and/or a solution stack from which the client can createsoftware interfaces and applications, e.g., Microsoft Azure). SaaS mayinclude, e.g., software hosted by a service provider and accessible overa network (e.g., the software for the application and/or the dataassociated with that software application may be kept on the network,e.g., Google Apps, SalesForce). DaaS may include, e.g., providingdesktop, applications, data, and/or services for the user over a network(e.g., providing a multi-application framework, the applications in theframework, the data associated with the applications, and/or servicesrelated to the applications and/or the data over the network, e.g.,Citrix). The foregoing is intended to be exemplary of the types ofsystems and/or methods referred to in this application as “cloud” or“cloud computing” and should not be considered complete or exhaustive.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components.

The term module, as used in the foregoing/following disclosure, mayrefer to a collection of one or more components that are arranged in aparticular manner, or a collection of one or more general-purposecomponents that may be configured to operate in a particular manner atone or more particular points in time, and/or also configured to operatein one or more further manners at one or more further times. Forexample, the same hardware, or same portions of hardware, may beconfigured/reconfigured in sequential/parallel time(s) as a first typeof module (e.g., at a first time), as a second type of module (e.g., ata second time, which may in some instances coincide with, overlap, orfollow a first time), and/or as a third type of module (e.g., at a thirdtime which may, in some instances, coincide with, overlap, or follow afirst time and/or a second time), etc. Reconfigurable and/orcontrollable components (e.g., general purpose processors, digitalsignal processors, field programmable gate arrays, etc.) are capable ofbeing configured as a first module that has a first purpose, then asecond module that has a second purpose and then, a third module thathas a third purpose, and so on. The transition of a reconfigurableand/or controllable component may occur in as little as a fewnanoseconds, or may occur over a period of minutes, hours, or days.

In some such examples, at the time the component is configured to carryout the second purpose, the component may no longer be capable ofcarrying out that first purpose until it is reconfigured. A componentmay switch between configurations as different modules in as little as afew nanoseconds. A component may reconfigure on-the-fly, e.g., thereconfiguration of a component from a first module into a second modulemay occur just as the second module is needed. A component mayreconfigure in stages, e.g., portions of a first module that are nolonger needed may reconfigure into the second module even before thefirst module has finished its operation. Such reconfigurations may occurautomatically, or may occur through prompting by an external source,whether that source is another component, an instruction, a signal, acondition, an external stimulus, or similar.

For example, a central processing unit of a personal computer may, atvarious times, operate as a module for displaying graphics on a screen,a module for writing data to a storage medium, a module for receivinguser input, and a module for multiplying two large prime numbers, byconfiguring its logical gates in accordance with its instructions. Suchreconfiguration may be invisible to the naked eye, and in someembodiments may include activation, deactivation, and/or re-routing ofvarious portions of the component, e.g., switches, logic gates, inputs,and/or outputs. Thus, in the examples found in the foregoing/followingdisclosure, if an example includes or recites multiple modules, theexample includes the possibility that the same hardware may implementmore than one of the recited modules, either contemporaneously or atdiscrete times or timings. The implementation of multiple modules,whether using more components, fewer components, or the same number ofcomponents as the number of modules, is merely an implementation choiceand does not generally affect the operation of the modules themselves.Accordingly, it should be understood that any recitation of multiplediscrete modules in this disclosure includes implementations of thosemodules as any number of underlying components, including, but notlimited to, a single component that reconfigures itself over time tocarry out the functions of multiple modules, and/or multiple componentsthat similarly reconfigure, and/or special purpose reconfigurablecomponents.

To the extent that formal outline headings are present in thisapplication, it is to be understood that the outline headings are forpresentation purposes, and that different types of subject matter may bediscussed throughout the application (e.g., device(s)/structure(s) maybe described under process(es)/operations heading(s) and/orprocess(es)/operations may be discussed under structure(s)/process(es)headings; and/or descriptions of single topics may span two or moretopic headings). Hence, any use of formal outline headings in thisapplication is for presentation purposes, and is not intended to be inany way limiting.

Throughout this application, examples and lists are given, withparentheses, the abbreviation “e.g.,” or both. Unless explicitlyotherwise stated, these examples and lists are merely exemplary and arenon-exhaustive. In most cases, it would be prohibitive to list everyexample and every combination. Thus, smaller, illustrative lists andexamples are used, with focus on imparting understanding of the claimterms rather than limiting the scope of such terms.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations are not expressly set forth herein for sakeof clarity.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

Although user 105 is shown/described herein, e.g., in FIG. 1, and otherplaces, as a single illustrated figure, those skilled in the art willappreciate that user 105 may be representative of one or more humanusers, robotic users (e.g., computational entity), and/or substantiallyany combination thereof (e.g., a user may be assisted by one or morerobotic agents) unless context dictates otherwise. Those skilled in theart will appreciate that, in general, the same may be said of “sender”and/or other entity-oriented terms as such terms are used herein unlesscontext dictates otherwise.

In some instances, one or more components may be referred to herein as“configured to,” “configured by,” “configurable to,” “operable/operativeto,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc.Those skilled in the art will recognize that such terms (e.g.“configured to”) generally encompass active-state components and/orinactive-state components and/or standby-state components, unlesscontext requires otherwise.

It is noted that “wearable computer” is used throughout thisspecification, and in the examples given, it is generally a wearablecomputer that captures images. However, this is merely for exemplarypurposes. The same systems may apply to conventional digital cameras,and any other camera, including security cameras, surveillance cameras,motor vehicle mounted cameras, road/traffic cameras, cameras atautomated teller machines, and the like.

Referring now to FIG. 1, in an embodiment, an entity, e.g., a user of aprivacy beacon, e.g., user 2105, e.g., a person, e.g., “Jules Caesar,”may be associated with a “Don't Capture Me” (hereinafter “DCM”) privacybeacon, e.g., DCM Beacon 2110. In an embodiment, a DCM beacon may beactive, e.g., may contain circuitry and be an active unit, e.g.,something wearable, e.g., on a piece of clothing, or on a ring, or on adrone associated with the user. In an embodiment, the DCM beacon may bepassive, e.g., it may be something that can be detected in theelectromagnetic spectrum, or can be otherwise detected but does notcontain any circuitry or advanced logic gates of its own. In anembodiment, the DCM beacon may be a combination of the two.

In an embodiment, a DCM beacon may be detectable by a machine or a humanbeing (e.g., a stop sign painted on a user's forehead may be a DCMbeacon). In an embodiment, a DCM beacon may be detectable by aparticular type of machine, structure, or filter, and may be otherwiseundetectable or difficult to detect through human senses. For example,in an embodiment, a DCM beacon may be seen using ultraviolet or infraredlight, or a DCM beacon may emit light outside the visible spectrum. Inan embodiment, a DCM beacon may be visible or detectable after a filteris applied, e.g., a DCM beacon may be visible after a red filter isapplied, or after a transformation is applied to a captured image, e.g.,a Fourier transformation.

In an embodiment, a DCM beacon may be detected optically. In anotherembodiment, a DCM beacon may be detected by sensing a different kind ofwave emitted by a DCM beacon, e.g., a wave in the nonvisibleelectromagnetic spectrum, a sound wave, an electromagnetic wave, and thelike. In an embodiment, a DCM beacon may use quantum entanglement (e.g.,through use of an entanglement-based protocol, among others).

In an embodiment, a DCM beacon may transmit data, e.g., a terms ofservice for the user (e.g., user 2105) for which the DCM beacon (e.g.,DCM beacon 2110) is associated or linked. In an embodiment, a DCM beaconmay be encoded with a location of data, e.g., a web address of a serverwhere terms of service for the user (e.g., user 2105) for which the DCMbeacon (e.g., DCM beacon 2110) is associated.

In an embodiment, a DCM beacon may be provided by a drone, of any size,e.g., nanometers to full-sized aircraft, that is associated with theuser.

In an embodiment, a DCM beacon may be provided by a piece of electronicsthat a user carries, e.g., a cellular telephone, tablet, watch, wearablecomputer, or otherwise.

In an embodiment, a DCM beacon may be embedded in the user, ingested bythe user, implanted in the user, taped to the skin of the user, or maybe engineered to grow organically in the user's body.

In an embodiment, a DCM beacon may be controlled by a magnetic field orother field emitted by a user, either through a user's regularelectromagnetic field or through a field generated by a device, local orremote, associated with the user.

Referring again to FIG. 1, in an embodiment, a different user, e.g., awearable computer user 3105, may have a wearable computer 3100. Awearable computer may be a pair of eyeglasses, a watch, jewelry,clothing, shoes, a piece of tape placed on the user's skin, it may beingested by the user or otherwise embedded into the user's body.Wearable computer 3100 may be a piece of electronics carried by a user3105. Wearable computer 3100 may not be a “wearable” computer in atraditional sense, but may be a laptop computer, tablet device, orsmartphone carried by a user. In an embodiment, wearable computer 3100may not be associated with a user at all, but may simply be a part of asurveillance system, e.g., a security camera, or a camera at anAutomated Teller Machine (“ATM”).

Wearable Computer that Captures the Image (FIGS. 1-I; 1-J, 1-N, 1-O).

Referring now to FIG. 1, e.g., FIG. 1-J, wearable computer 3100 mayinclude a wearable computer image capturing device 3110, e.g., a lens.Wearable computer image capturing device 3110 may include functionalityto capture images, e.g., an image sensor, e.g., a charge-coupled device(“CCM”) or a complementary metal-oxide semiconductor (“CMOS”), ananalog-to digital converter, and/or any other equipment used to convertlight into electrons. Wearable computer image capturing device 3110 maycapture the optical data, which may remain as light data, or may beconverted into electrons through an image sensor, as raw data. This rawdata, e.g., raw data 2200 may be captured by the optical image dataacquiring module 3120 of wearable computer 3100. Optical image dataacquiring module 3120 may be configured to acquire an image, e.g., animage of user 2105. As described above, a DCM beacon 2110 may beassociated with user 2105. In an embodiment, at this point in theoperation of wearable computer 3100, no processing has been performed onthe raw image data 2200.

Although not pictured here, wearable computer image capturing device3110 may also include circuitry to detect audio (e.g., a microphone)and/or video (e.g., the ability to capture frames above a certain rateof frames per second). This circuitry and its related explanation havebeen omitted to maintain simplicity of the drawing, however, throughthis application, “raw image data 2200” should be considered to alsopossibly include still pictures, video, and audio, in some embodiments.

Referring now to FIG. 1-I, in an embodiment, wearable computer 3100 thenmay transfer the raw/optical image data 2200 to an image path splittingmodule 3130. This splitting path may be optical, e.g., a set ofmirrors/lenses, for the case in which raw image data 2200 is still inoptical form, or digital, e.g., through use of known electrical signalsplitters. Image path splitting module 3130 may be implemented ashardware, software, or a combination thereof.

Referring again to FIG. 1, e.g., FIG. 1-I, in an embodiment, the north(upper) branch, as illustrated in FIG. 1, transmits the raw image data2200 to an image prior-to-processing encryption module 3150. Imageprior-to-processing encryption module 3150 may receive the raw imagedata 2200. From there, image prior-to-processing encryption module 3150may acquire an encryption key that is device-specific, e.g., wearablecomputer device specific encryption key 3182. In an embodiment, wearablecomputer device-specific encryption key 3182 may be stored in wearablecomputer device memory 3180, which also may include encrypted imagestorage 3184, and a wearable computer user-specific encryption key 3186.In another embodiment, device-specific encryption key 3182 may beretrieved from elsewhere, e.g., cloud storage. In another embodiment,device-specific encryption key 3182 may be generated in real time by thedevice. In another embodiment, device-specific encryption key 3182 maybe generated in real time by the device based on random user input(e.g., the last five words spoken by the device and recorded).

In an embodiment, image prior-to-processing encryption module 3150 maygenerate encrypted image data 2210. Encrypted image data 2210 may bestored in encrypted image storage 3184 of wearable computer devicememory 3180. In an embodiment, encrypted image data 2210 also may betransmitted to central server encrypted data and beacon metadatatransmission module 3170.

Referring again to FIGS. 1-I and FIG. 1-N, in an embodiment, the south(lower) branch, as illustrated in FIG. 1, may transmit the raw imagedata 2200 to a DCM beacon detecting module 3140. In an embodiment, DCMbeacon detecting module 3140 may include one or more of optics-based DCMbeacon detecting module 3142, which may be configured to detect the DCMbeacon in an optical signal (e.g., light). In an embodiment, DCM beacondetecting module 3140 may include digital image processing-based DCMbeacon detecting module 3144, which may be configured to detect the DCMbeacon in a converted electron signal (e.g., data signal). In anembodiment, DCM beacon detecting module 3140 is configured to detect apresence or an absence of a DCM beacon, e.g., DCM beacon 2110,associated with the entity (e.g., user 2105, e.g., “Jules Caesar”),without performing any additional processing on the image, or releasingthe image for other portions of wearable computer 3100 to use. In anembodiment, for example, raw image data 2200 is not stored in devicememory of wearable computer 3100 in a form that is accessible to otherapplications and/or programs available to wearable computer 3100 orother computing devices that may communicate with wearable computer3100. For example, a user 3105 of wearable computer 3100 may not, atthis stage in processing, capture the raw data 2200 and upload it to asocial networking site, e.g., Facebook. In an embodiment, DCM beacondetecting module 3140 may be implemented in hardware, which may preventusers or third parties from bypassing the DCM beacon detecting module3140, without disassembling the device and physically altering thecircuit/logic.

Referring now to FIG. 1-N, in an embodiment, the DCM beacon detectingmodule 3140 may detect the DCM beacon 2110. For example, in theexemplary embodiment shown in FIG. 1, DCM beacon detecting module 3140may detect the DCM beacon 2110 that is associated with user 2105, e.g.,Jules Caesar. Thus, DCM beacon detecting module 3140 now knows to lockthe image data and prevent unencrypted image data from being accessed onthe device. Although not shown in this example, if the DCM beacon hadnot been found, then in an embodiment, the image data 2200 would havebeen released for use by the device, e.g., for uploading to socialnetwork or cloud storage, for example.

In an embodiment, the detected DCM beacon 2110 associated with JulesCaesar may be transmitted to DCM beacon metadata generating module 3160.DCM beacon metadata generating module 3160 may generate metadata basedon the detection of the beacon. The metadata may be as simple as “theimage data contains a privacy beacon,” e.g., Boolean data. In anembodiment, the metadata may be more complex, and may identify the userassociated with the privacy beacon, e.g., the metadata may describe “Aprivacy beacon associated with Jules Caesar has been found in the imagedata.” In another embodiment, the metadata may include the terms ofservice associated with the personality rights of Jules Caesar, anexample of which terms of service will be provided in more detailherein.

In an embodiment, the detected DCM beacon 2110 may be very simple (e.g.,optically detectable), and to obtain/generate metadata associated withthe detected DCM beacon 2110, DCM beacon metadata generating module 3160may include a DCM server contacting module 3162, which may contact oneor more entities to obtain more information regarding the DCM beacon2110. The DCM beacon metadata generating module 3160 may, in someembodiments, transmit the DCM beacon, or the image in which the DCMbeacon was captured, to the external entity, in order to obtain moreaccurate data. For example, the DCM server contacting module 3162 maycontact service term management server 5000, which may have DCM beaconregistry 5010, which will be discussed in more detail further herein.

In an embodiment, DCM beacon metadata generating module 3160 maygenerate the DCM beacon metadata 2230, and transfer DCM beacon metadata2230 to central server encrypted data and beacon metadata transmissionmodule 3170.

Referring again to FIG. 1, e.g., FIG. 1-I, central server encrypted dataand beacon metadata transmission module 3170 may receive the encryptedimage data 2210 and the DCM beacon metadata 2230 (e.g., see FIG. 1-N).In an embodiment, central server encrypted data and beacon metadatatransmission module 3170 may facilitate the transmission of encryptedimage data 2210 and DCM beacon metadata 2230 to a server, e.g., wearablecomputer encrypted data receipt and determination server 4000, whichwill be discussed in more detail herein. In an embodiment, centralserver encrypted data and beacon metadata transmission module 3170 mayinclude one or more of DCM beacon metadata transmission module 3172,which may be configured to transmit the DCM beacon metadata 2230, andencrypted data transmission module 3174, which may be configured totransmit the encrypted image data 2210.

Wearable Computer Server (FIGS. 1-H, 1-G)

Referring again to FIG. 1, e.g., FIG. 1-H, in an embodiment, a systemmay include a wearable computer server, e.g., wearable computerencrypted data receipt and determination server 4000. In an embodiment,a wearable computer server may be provided by a manufacturer of thewearable device 3100. In an embodiment, a wearable computer server maybe provided by a developer of one or more software applications for thewearable device 3100. In an embodiment, wearable computer server 4000may not have a direct relationship with wearable device 3100 prior toreceiving the encrypted image data and the DCM beacon metadata 2230, aswill be discussed in more detail herein. In an embodiment, a wearablecomputer server 4000 may be implemented at a home computer of a user,for example, and may communicate only with wearable devices that areassociated with that user. In another embodiment, a wearable computerserver 4000 may communicate with many wearable devices 3100, which mayor may not have some relationship. In an embodiment, wearable computerserver 4000 may communicate with one or more wearable devices 3100through use of a communication network, which may use any known form ofdevice communication. In an embodiment, wearable computer server 4000may be chosen by wearable device 3100, either due to proximity or due toone or more properties or characteristics of wearable computer server4000. In an embodiment, wearable computer server 4000 may be free toagree or disagree to process DCM beacon and image data received fromvarious wearable devices 3100. In an embodiment, wearable computerserver 4000 may be distributed across many computers and/or servers.

In an embodiment, wearable computer encrypted data receipt anddetermination server 4000 may include an encrypted data and beaconmetadata reception module 4100. Encrypted data and beacon metadatareception module 4100 may receive encrypted image data 2210 and DCMbeacon metadata 2230 from wearable computer 3100, e.g., central serverencrypted data and beacon metadata transmission module 3170. In anembodiment, encrypted data and beacon metadata reception module 4100 mayinclude a DCM beacon metadata reception module 4104. DCM beacon metadatareception module 4104 may be configured to acquire a privacy metadata,e.g., DCM beacon metadata 2230, corresponding to a detection of a DCMbeacon, e.g., DCM beacon 2110, in the one or more images captured by theimage capture device, e.g., wearable computer 3100. In an embodiment,encrypted data and beacon metadata reception module 4100 may includeencrypted data reception module 4102. In an embodiment, encrypted datareception module 4102 may be configured to acquire one or more of ablock of encrypted data corresponding to one or more images thatpreviously have been encrypted, e.g., encrypted image data 2210. In anembodiment, encrypted data module 4102 may transmit, or facilitate thetransmission of, encrypted image data 2210 to an entity that willperform a secondary detection of the privacy beacon, e.g., DCM beacondetection test duplicating server 4800, which will be discussed in moredetail further herein.

Referring again to FIG. 1-H, in an embodiment, encrypted data and beaconmetadata reception module 4100 may transmit the received DCM beaconmetadata to DCM beacon metadata reading module 4120. If the DCM beaconmetadata 2230 indicates that a DCM beacon was not found, then, in anembodiment, processing may transfer to module 4220, which will bediscussed in more detail further herein. In the example shown in FIG. 1,the DCM beacon 2110 associated with Jules Caesar was found, and the DCMbeacon metadata 2230 indicates this state to DCM beacon metadata readingmodule 4120.

Referring now to FIG. 1-G, in an embodiment, when the presence of theDCM beacon 2110 is determined through the DCM beacon metadata, e.g., DCMbeacon metadata 2230, then a DCM beacon TOS retrieval module 4122 mayretrieve term data from a location, which may be a remote location,e.g., a DCM beacon management server 5100, which will be discussed inmore detail further herein. In an embodiment, DCM beacon TOS retrievalmodule 4122 may retrieve term data that includes a terms of service thatspecifies one or more conditions in which the image containing the DCMbeacon 2110 may be used. In an embodiment, the TOS may also specify oneor more penalties for using the personality rights that may beassociated with the image, without acquiring permission or paying alicensing fee prior to releasing or utilizing the image. In anembodiment, the TOS also may include language forcing the entity thatviewed the privacy beacon to accept the TOS upon viewing of the beacon.The TOS will be described in more detail with respect to modules 5000and 5100.

Referring again to FIG. 1-G, in an embodiment, wearable computerencrypted data receipt and determination server 4000 also may include anencrypted data value calculation module 4130. Encrypted data valuecalculation module 4130 may use one or more algorithms or other methodsof inducing or deducing an estimate regarding how much advertising orother revenue may be garnered by using the images containing the entityassociated with the privacy beacon. For example, in an embodiment,encrypted data value calculation module 4130 may include a facialrecognition program to recognize the person or persons associated withthe beacon. In another embodiment, however, this may not be necessary,because the DCM beacon metadata and/or the ToS may identify the person.In an embodiment, encrypted data value calculation module 4130 may usevarious heuristics to calculate ad revenue, e.g., based on models usedby popular advertising methods, or based on prior releases of images ofthe person associated with the DCM beacon 2110. In an embodiment, module4130 may use social networking to acquire a focus group and test theimage on the focus group, in order to assist in revenue determination.For example, in the example shown in FIG. 1, the image in question is ofJules Caesar, who is the reclusive leader of the Roman Empire, and sothe ad revenue generated from having an actual picture of Jules Caesar,or a video of Jules Caesar drinking a mead-and-tonic, may have high netvalue.

Referring again to FIG. 1-G, in an embodiment, the ToS acquired from DCMbeacon TOS retrieval module 4122, and the encrypted data valuationcalculated from encrypted data value calculation module 4130 may be sentto release of encrypted data determination module 4140. Release ofencrypted data determination module 4140 may make a determination, atleast partly based on the acquired metadata, and at least partly basedon a value calculation based on the representation of the feature of theperson associated with the DCM beacon 2110 (e.g., Jules Caesar drinkinga mead-and-tonic). That determination may be regarding whether to allowan action, e.g., processing, decryption, distribution, editing,releasing, sharing, saving, posting to a social network, and the like,of the image. In an embodiment, the decision may be based on whether thepotential advertising revenue outweighs the potential damages retrievedfrom the terms of service. In an embodiment, this calculation may be astrict number comparison (e.g., is “revenue” greater than “damages”). Inan embodiment, the calculation may include more complex factors, e.g.,likelihood of success on a damages claim, likelihood that revenues willincrease, secondary revenue factors from increased traffic and/or brandawareness, and the like. In addition, in an embodiment, the comparisonmay not be strictly less than/greater than, e.g., in a risk adversealgorithm, if the numbers are close, then the determination may be tonot release the encrypted data, even if the potential ad revenue iscalculated as larger than the potential damages by a small amount.

Referring again to FIG. 1-G, if the determination made by release ofencrypted data determination module 4140 is “NO,” e.g., the potentialrevenue is less than the potential damages, then the encrypted data 2210is moved to an encrypted data holding and/or quarantine module 4150. Inan embodiment, the data from encrypted data holding and/or quarantinemodule 4150 is deleted after a predetermined time period, e.g., sevendays. In an embodiment, the data is simply stored, encrypted and lockedaway. In an embodiment, the encrypted image data 2210 may be transmittedto an ad replacement value determination server 4400, shown in FIG. 1-F,which will be discussed in more detail herein.

Referring again to FIG. 1-G, if the determination made by release ofencrypted data determination module 4140 is “YES,” e.g., the potentialrevenue is more than the potential damages, then the encrypted data 2210is transferred to encrypted data decryption enabling module 4152, shownin FIG. 1-H. In an embodiment, encrypted data decryption enabling module4152 may be configured to determine whether to perform decryption of atleast a portion of the encrypted data 2210 based on the result frommodule 4140 by transmitting the encrypted image data 2210 to wearablecomputer acquired encrypted data decryption and re-encryption server4200, which will be discussed in more detail.

Wearable Computer Acquired Encrypted Data Decryption and Re-EncryptionServer 4200 (FIGS. 1-L and 1-M)

Referring now to FIG. 1-M, in an embodiment, the system may includewearable computer acquired encrypted data decryption and re-encryptionserver 4200. In an embodiment, wearable computer acquired encrypted datadecryption and re-encryption server 4200 may be a portion of wearablecomputer server 4000. In an embodiment, however, wearable computeracquired encrypted data decryption and re-encryption server 4200 may bea different server than wearable computer server 4000, and may becontrolled by a different entity. For example, in an embodiment, theowner of the wearable computer 3100 hardware may control wearablecomputer server 4000. After the decision is made to decrypt the data atthe wearable computer server 4000, control may be handed off to adifferent server in control of software on the wearable computer, e.g.,software that handles pictures taken by the wearable computer 3100. Inanother embodiment, wearable computer acquired encrypted data decryptionand re-encryption server 4200 may be controlled by a socialnetworking/media site, e.g., Facebook, who may have an agreement toacquire the image data at the same time as the device.

Referring again to FIG. 1-M, in an embodiment, wearable computeracquired encrypted data decryption and re-encryption server 4200 mayinclude encrypted data acquiring module 4210, which may acquire theencrypted image data 2210 from the wearable computer server 4000. In anembodiment, wearable computer acquired encrypted data decryption andre-encryption server 4200 may include a privacy metadata acquiringmodule 4220, which may acquire privacy metadata from module 4120, if theDCM beacon was never detected and the image is free to be used. Forexample, in an embodiment, image data with no DCM beacon may be treatedsimilarly to image data with a DCM beacon, but that has been determinedto have an advertising value greater than a potential damages value. Forexample, in an embodiment, image data with no DCM beacon may be treatedas image data with potential damages value of zero.

Referring again to FIG. 1-M, in an embodiment, wearable computeracquired encrypted data decryption and re-encryption server 4200 mayinclude data indicating profitability of image with DCM beacon acquiringmodule 4230, which may receive data from module 4150 of wearablecomputer server 4000 indicating that the image should be decryptedregardless of the DCM beacon because of its potential profitability.

Referring again to FIG. 1-M, in an embodiment, wearable computeracquired encrypted data decryption and re-encryption server 4200 mayinclude image data decryption preparation module 4240, which may receivedata from one or more of data indicating profitability of image with DCMbeacon acquiring module 4230, encrypted data acquiring module 4210, andprivacy metadata acquiring module 4220. In an embodiment, module 4240may prepare the image or images for decryption, e.g., performpre-processing, check image integrity, reconfirm the privacy beaconcalculations, and the like.

Referring now to FIG. 1-L, wearable computer acquired encrypted datadecryption and re-encryption server 4200 may include device-specific keyretrieving module 4250 which may retrieve the device-specific key usedto encrypt/decrypt the encrypted image data 2210. In an embodiment,device-specific key retrieving module 4250 may include a device-specifickey retrieving from device module 4252, which may be configured toretrieve the device-specific key directly from the device that encryptedthe image, e.g., wearable computing device 3100. In an embodiment,device-specific key retrieving module 4250 may include a device-specifickey retrieving from server module 4254, which may be configured toretrieve the device-specific key from a server, e.g., from wearablecomputer encrypted data receipt and determination server 400, or fromDCM beacon detection test duplicating server 4800, or from anotherserver not depicted in FIG. 1.

Referring again to FIG. 1-L, in an embodiment, image data decryptionwith device-specific key module 4260 may take the device-specific keyretrieved from module 4250, and apply it to the encrypted image data2210 to generate decrypted image data 2280, as shown by the icon withthe unlocked lock in FIG. 1-L.

Referring again to FIG. 1-L, the image data has been decrypted. However,to protect security, in some embodiments, the data may be re-encryptedwith a key that is not tied to a specific device, but may be tied to aspecific user of the device, e.g., the key may be related to user 3105,rather than wearable device 3100. This embodiment will be described inmore detail herein. This embodiment allows the re-encrypted data to besecurely sent to a different device belonging to the user, e.g., a smartTV, a home computer, a video game system, or another portable electronicdevice, e.g., a cellular smartphone. In an embodiment, the re-encryptionwith a user specific key may be omitted.

In an embodiment, wearable computer acquired encrypted data decryptionand re-encryption server 4200 may include a user-specific key retrievingmodule 4270, that may be configured to obtain, through generation,acquisition, reception, or retrieval, of a user-specific encryption key.The user-specific encryption key may be delivered to image dataencrypting with user-specific key module 4280, which, in an embodiment,also may receive the decrypted image data 2280.

Referring again to FIG. 1-L, in an embodiment, image data encryptingwith user-specific key module 4280 may be configured to encrypt theblock of decrypted data through use of a unique user code that isrelated to the user 3105 of the wearable device 3100. Theagain-encrypted image data then may be transferred to encrypted imagedata transmitting module 4290. In an embodiment, encrypted image datatransmitting module 4290 may transmit the image data that has beenencrypted with a user-specific key to one or more other devices, whichwill be discussed in more detail herein.

Computing Device that Receives the Image Data (FIGS. 1-S and 1-T).

Referring now to FIG. 1-S, in an embodiment, the system may include acomputing device 3200, which may be a wearable computer or other device.In an embodiment, computing device 3200 may be the same as wearablecomputer 3100, but it does not necessarily have to be the same. In anembodiment, computing device 3200 receives the image data. In anembodiment, as described above, the received image data has beenencrypted with a user-specific code. Thus, in such an embodiment,computing device 3200 may be associated with user 3105 of the wearablecomputing device 3100. For example, a user 3105 may have a wearablecomputing device 3100 that captures images of people. After processingthose images at the server 4000, for example, the images, which, in someembodiments, now may be encrypted with a user-specific code, may betransmitted to computing device 3200, which may be the user 3105's homemedia center back at her house. In another embodiment, computing device3200 may be user 3105's laptop device, or user 3105's smartphone ortablet device. And, as previously mentioned, in another embodiment,computing device 3200 may simply be the user 3105's wearable computingdevice 3100 that captured the images originally.

In an embodiment, the computing device 3200 and the wearable computingdevice 3100 pictured in FIG. 1 are the same device. In an embodiment,the encryption, transmission to a server, decryption, and transmissionback, may occur invisibly to the user 3105, e.g., to the user 3105 ofthe wearable computing device 3100, the images are available to herafter they are recorded and saved, with a delay that is not specified.In some embodiments, the user 3105 may not be informed of the path takenby the captured image data.

In an embodiment, wearable computing device 3100 may include anencrypted image data receiving module 3210 configured to acquire thedata encrypted by the user-specific key code from encrypted image datatransmitting module 4290 of wearable computer 4200. In an embodiment,computing device 3200 may include image data release verificationacquiring module 3220, which may be configured to determine that theimages received from the encrypted image data transmitting module 4290of wearable computer 4200 have been approved for release and/or use. Inan embodiment, the determination may be made based on the ground thatthe images are encrypted with a user-specific key rather than a devicespecific key, if it is possible to tell from the encrypted information(e.g., in some embodiments, different types of encryption that may leavea different “signature” may be used). In an embodiment, thedetermination may be made by again analyzing the image data. In anembodiment, image data release verification acquiring module 3220 mayinclude encrypted image data analysis module 3222 which may performanalysis on the encrypted image data, including, but not limited to,reading metadata attached to the encrypted image data, to verify thatthe received encrypted image data is approved for release and/orprocessing. In an embodiment, image data release verification acquiringmodule 3220 may include release verification data retrieving module3224, which may be configured to obtain release verification data fromthe device that performed the verification, e.g., server 4000, or from adifferent device.

Referring now to FIG. 1-T, in an embodiment, computing device 3200 mayinclude device memory 3280. Device memory 3280 may store the wearablecomputer user-specific encryption/decryption key 3286, which may be usedto decrypt the received encrypted image data. In an embodiment, devicememory 3280 also may include encrypted image storage 3284, which mayinclude one or more image data, which may be encrypted.

Referring again to FIG. 1-S, in an embodiment, computing device 3200 mayinclude user-specific decryption key obtaining module 3230, which mayobtain the user-specific encryption/decryption key. In an embodiment,user-specific decryption key obtaining module 3230 may includeencryption/decryption key external source obtaining module 3232, whichmay be configured to obtain the encryption/decryption key from anexternal source, e.g., server 4000. In an embodiment, user-specificdecryption key obtaining module may include encryption/decryption keymemory retrieving module 3234, which may be configured to retrieve theencryption/decryption key from device memory 3280 of computing device3200.

Referring again to FIG. 1-S, in an embodiment, computing device 3200 mayinclude image decryption module 3240, which may use the user-specificencryption/decryption key to decrypt the image data. In an embodiment,the decrypted image data then may be sent to decrypted image releasemodule 3250, where the clear image data may be accessed by the device,and transmitted to other locations, posted to social networking or cloudstorage, be shared, manipulated, saved, edited, and otherwise have openaccess to the decrypted image data.

Ad Replacement Value Determination Server (FIG. 1-F).

Referring back to FIG. 1-G, as discussed briefly above, release ofencrypted data determination module 4140 may determine not to releasethe encrypted data, which may be stored in an encrypted data holdingand/or quarantine module 4150. In an embodiment, the encrypted data andthe DCM beacon may be transmitted to an ad replacement valuedetermination server, as shown in FIG. 1-F.

Referring now to FIG. 1-F, in an embodiment, the system may include anad replacement value determination server 4400. Ad replacement valuedetermination server 4400 may take the encrypted image data anddetermine if there is a way to monetize the images such that themonetization may outweigh the potential damages. For example, adreplacement value determination server 4400 may calculate potentialearnings and limited damages liability, if, for example, an entity withthe DCM beacon, e.g., Jules Caesar, is instead shown with anadvertisement where his head would normally be. In an embodiment, adreplacement value server may be controlled by a different entity thanserver 4000, and there may be an agreement in place for the adreplacement value determination server 4400 to receive encrypted datafor which the server 4000 decides it does not want to allowdistribution. For example, ad replacement value server 4400 may be runby a smaller social networking site that cares less about potentialdamages because they have fewer assets, or are less risk-averse. Inanother embodiment, ad replacement value determination server 4400 maybe part of server 4000, and it may be a practice of server 4000 to sendan encrypted image for further analysis after the server 4000 determinesthat the image is not likely to be profitable without modification.

Referring again to FIG. 1-F, in an embodiment, ad replacement valuedetermination server 4400 may include a DCM beacon metadata receptionmodule 4410 configured to receive the DCM beacon metadata from thewearable computer encrypted data receipt and determination server 4000.In an embodiment, ad replacement value determination server 4400 mayinclude an encrypted data reception module 4420 that may be configuredto receive the encrypted data from the wearable computer encrypted datareceipt and determination server 4000, e.g., from the encrypted dataholding module 4150.

Referring again to FIG. 1-F, in an embodiment, ad replacement valuedetermination server 4400 may include a DCM beacon term acquiring module4430, which may acquire one or more terms of service from service termmanagement server 5000 and/or DCM beacon management server 5100,similarly to DCM beacon terms-of-service retrieval module 4122 ofwearable computer encrypted data receipt and determination server 4000.In an embodiment, DCM beacon term acquiring module may include DCMbeacon remote retrieval module 4432. In an embodiment, DCM beacon termacquiring module may be configured to retrieve term data from a remotelocation, e.g., service term management server 5000, which term data maycorrespond to a term of service associated with a release of image datathat includes the person with which the DCM beacon is associated, e.g.,Jules Caesar.

Referring again to FIG. 1-F, in an embodiment, ad replacement valuedetermination server 4400 may include an encrypted data valuecalculation with standard ad placement module 4440. In an embodiment,standard ad placement module 4440 may perform a similar calculation asencrypted data value calculation module 4130 of wearable computerencrypted data receipt and determination server 4000. In an embodiment,for example, encrypted data value calculation with standard ad placementmodule 4440 may calculate whether an estimated advertising revenue fromone or more advertisement images placed in the encrypted image data willbe greater than an estimated potential liability for distribution of theimages. In an embodiment, the estimated potential liability is based atleast in part on the terms of service which may be retrieved by the DCMbeacon term acquiring module 4430.

Referring again to FIG. 1-F, in an embodiment, ad replacement valuedetermination server 4400 may include encrypted image data modificationwith intentionally obscuring ad placement module 4450. In an embodiment,encrypted image data modification with intentionally obscuring adplacement module 4450 may be configured to modify the encrypted imagedata (e.g., which, in some embodiments, may require limited decryptionand then re-encryption) by replacing one or more areas associated withthe entity related to the DCM beacon, e.g., Jules Caesar's face (e.g.,or in another embodiment, Jules Caesar's genitalia, if, e.g., it was anaked picture of Jules Caesar), with one or more advertisement images.

Referring again to FIG. 1-F, in an embodiment, ad replacement valuedetermination server 4400 may include modified encrypted data valuecalculation with intentionally obscuring ad placement module 4460. In anembodiment, modified encrypted data value calculation with intentionallyobscuring ad placement module 4460 may be configured to calculate anestimated advertising revenue from the modified image data. In anembodiment, the modified image data then may be distributed throughmodified encrypted data distributing module 4470.

Tracking Server (FIG. 1-E).

Referring now to FIG. 1-E, in an embodiment, a system may includetracking server 9000. Tracking server 9000 may be configured to log useof a “Don't Capture Me” (hereinafter “DCM”) beacon by one or multipleusers. In an embodiment, tracking server 9000 may track active DCMbeacons, e.g., beacon 2110, through communication with said one or morebeacons. In an embodiment, tracking server may track DCM beacons throughother means, e.g., social networking and the like. The DCM beacon doesnot need to be an active DCM beacon in order to be tracked by trackingserver 9000.

In an embodiment, tracking server 9000 may include deployment of one ormore active and/or passive DCM beacons monitoring module 9010.Deployment of one or more active and/or passive DCM beacons monitoringmodule 9010 may include one or more of active DCM beacon monitoringmodule 9012 and passive DCM beacon monitoring/data gathering module9020. In an embodiment, passive DCM beacon monitoring/data gatheringmodule 9020 may gather data about the passive DCM beacon by observingit, e.g., through satellite video capture, through other image capturingdevices, e.g., phone cameras, security cameras, laptop webcams, and thelike, or through other means. In an embodiment, passive DCM beaconmonitoring/data gathering module 9020 may include user input module9022, which may receive an indication from a user, e.g., a switchflipped on a user's cell phone, indicating that the user is using theDCM beacon. In an embodiment, passive DCM beacon monitoring/datagathering module 9020 may include a device status module which tracks adevice with which the passive DCM beacon is associated, e.g., a wearablecomputer that is a shirt, or a cellular phone device in the pocket. Inan embodiment, passive DCM beacon monitoring/data gathering module 9020may include a social media monitoring module that monitors posts onsocial networking sites to determine if the DCM beacon is being used,and a location of the user.

Referring again to FIG. 1-E, in an embodiment, tracking server 9000 mayinclude a record of the deployment of the one or more active and/orpassive DCM beacons storing module 9030, which may be configured tostore a record of usage and/or detection logs of the DCM beacons thatare monitored. In an embodiment, record of the deployment of the one ormore active and/or passive DCM beacons storing module 9030 may store arecord of the deployment in deployment record storage 9032. In anembodiment, record of the deployment of the one or more active and/orpassive DCM beacons storing module 9030 may transmit all or portions ofthe recorded record through record of the deployment of one or moreactive and/or passive DCM beacons transmitting module 9040.

Service Term Management Server 5000 (FIG. 1-A)

Referring now to FIG. 1-A, in an embodiment, the system may includeservice term management server 5000, which may manage terms of servicethat are associated with a DCM beacon and/or a person. In an embodiment,service term management server 5000 may include a DCM beacon registry5010. In an embodiment, the DCM beacon registry 5010 may include one ormore of a user's name, e.g., Jules Caesar, a terms of service associatedwith Jules Caesar, which may be custom to Jules Caesar, or may be ageneric terms of service that is used for many persons, and variousrepresentations of portions of Jules Caesar, e.g., likeness, handprint,footprint, voiceprint, pictures of private areas, and the like.

Referring again to FIG. 1-A, in an embodiment, the system may include aterms of service generating module 5020. Terms of service generatingmodule 5020 may create a terms of service for the user Jules Caesar. Asample Terms of Service is shown in FIG. 1-A and is reproduced here. Itis noted that this is a condensed Terms of Service meant to illustratean exemplary operation of the system in the environment, andaccordingly, several necessary legal portions may be omitted.Accordingly, the example Terms of Service should not be considered as abinding, legal document, but rather a representation of what thebinding, legal document would look like, that would enable one skilledin the art to create a full Terms of Service.

Exemplary Terms of Service for User 2105 (Jules Caesar)

1. By capturing an image of any part of the user Jules Caesar(hereinafter “Image”), or providing any automation, design, resource,assistance, or other facilitation in the capturing of the Image, youagree that you have captured these Terms of Service and that youacknowledge and agree to them. If you cannot agree to these Terms ofService, you should immediately delete the captured Image. Failure to doso will constitute acceptance of these Terms of Service.

2. The User Jules Caesar owns all of the rights associated with theImage and any representation of any part of Jules Caesar thereof;

3. By capturing the Image, you agree to provide the User Jules Caesarjust compensation for any commercialization of the User's personalityrights that may be captured in the Image.

4. By capturing the Image, you agree to take all reasonable actions totrack the Image and to provide an accounting of all commercializationattempts related to the Image, whether successful or not.

5. By capturing the Image, you accept a Liquidated Damages agreement inwhich unauthorized use of the Image will result in mandatory damages ofat least, but not limited to, $1,000,000.

In an embodiment, terms of service generating module may include one ormore of a default terms of service storage module 5022, a potentialdamage calculator 5024, and an entity interviewing for terms of servicegeneration module. In an embodiment, default terms of service storagemodule 5022 may store the default terms of service that are used as atemplate for a new user, e.g., when Jules Caesar signs up for theservice, this is the terms of service that is available to him. In anembodiment, potential damage calculator 5024 may determine an estimateof how much in damages that Jules Caesar could collect for a breach ofhis personality rights. In an embodiment, for example, potential damagecalculator may search the internet to determine how much Jules Caesarappears on social media, blogs, and microblog (e.g., Twitter) accounts.In an embodiment, entity interviewing for terms of service generationmodule 5026 may create an online questionnaire/interview for JulesCaesar to fill out, which will be used to calculate potential damages toJules Caesar, e.g., through determining Jules Caesar's net worth, forexample.

In an embodiment, service term management server 5000 may include termsof service maintenance module 5030, which may maintain the terms ofservice and modify them if, for example, the user becomes more popular,or gains a larger online or other presence. In an embodiment, terms ofservice maintenance module 5030 may include one or more of a socialmedia monitoring module 5042, that may search social networking sites,and an entity net worth tracking module 5034 that may have access to theentity's online bank accounts, brokerage accounts, property indexes,etc., and monitor the entity's wealth.

In an embodiment, serviced term management server 5000 may include a useof representations of an entity detecting module 5040. In an embodiment,use of representations of an entity detecting module 5040 may includeone or more of a social media monitoring module 5042, a public photorepository monitoring module 5044, and a public blog monitoring module5046. In an embodiment, use of representations of an entity detectingmodule 5040 may track uses of representations, e.g., images, of the userJules Caesar, to try to detect violations of the terms of service, invarious forums.

DCM Beacon Management Server 5100 (FIG. 1-C)

Referring now to FIG. 1-C, in an embodiment, the system may include aDCM beacon management server 5100, which may be configured to manage theDCM beacon associated with a user, e.g., DCM beacon 2110 for user 2105,e.g., Jules Caesar. In an embodiment, DCM beacon management server 5100and service term management server 5000 may be the same server. Inanother embodiment, DCM beacon management server 5100 and service termmanagement server 5000 may be hosted by different entities. For example,a specialized entity may handle the terms of service generation, e.g., avaluation company that may be able to determine a net “social network”worth of a user, e.g., Jules Caesar, and use that to fashion the termsof service.

Referring again to FIG. 1-C, in an embodiment, DCM beacon managementserver 5100 may include DCM beacon communication with entity wanting toavoid having their image captured module 5110. DCM beacon communicationwith entity wanting to avoid having their image captured module 5110 maybe configured to communicate with a user, e.g., user 2105, e.g., JulesCaesar, and may handle the creation, generation, maintenance, andproviding of the DCM beacon 2110 to Jules Caesar, whether throughelectronic delivery or through conventional delivery systems (e.g.,mail, pickup at a store, etc.). In an embodiment, DCM beaconcommunication with entity wanting to avoid having their image capturedmodule 5110 may include one or more of DCM beacon transmission module5112, DCM beacon receiving module 5114, and DCM beacon generating module5116.

In an embodiment, DCM beacon management server 5100 may include entityrepresentation acquiring module 5120. Entity representation acquiringmodule 5100 may be configured to receive data regarding one or morefeatures of the user that will be associated with the DCM beacon. Forexample, the user might upload pictures of his body, face, privateparts, footprint, handprint, voice recording, hairstyle, silhouette, orany other representation that may be captured and/or may be deemedrelevant.

In an embodiment, DCM beacon management server 5100 may include DCMbeacon association with one or more terms of service and one or moreentity representations module 5130. In an embodiment, DCM beaconassociation with one or more terms of service and one or more entityrepresentations module 5130 may be configured to, after generation of aDCM beacon, obtain a terms of service to be associated with that DCMbeacon. In an embodiment, the terms of service may be received fromservice term management server 5000.

In an embodiment, DCM beacon management server 5100 may include a DCMbeacon capture detecting module 5140. DCM beacon capture detectionmodule 5140 may detect when a DCM beacon is captured, e.g., if it is anactive beacon, or it may receive a notification from various servers(e.g., server 4000) and/or wearable devices (e.g., wearable device 3100)that a beacon has been detected, if it is a passive DCM beacon.

In an embodiment, when a DCM beacon is detected, DCM beacon managementserver 5100 may include terms of service associated with DCM beacondistributing module, which may be configured to provide the terms ofservice associated with the DCM beacon to an entity that captured theimage including the DCM beacon, e.g., to module 4122 of wearablecomputer encrypted data receipt and determination server 4000, or DCMbeacon remote retrieval module 4430 of ad replacement valuedetermination server 4400, for example.

Wearable Computer with Optional Paired Personal Device 3300 (FIGS. 1-Qand 1-R)

Referring now to FIG. 1-R, in an embodiment, the system may include awearable computer 3300. Wearable computer 3300 may have additionalfunctionality beyond capturing images, e.g., it may also store a user'scontact list for emails, phone calls, and the like. In anotherembodiment, wearable computer 3300 may be paired with another devicecarried by a user, e.g., the user's smartphone device, which stores theuser's contact list. As will be described in more detail herein,wearable computer 3300 operates similarly to wearable computer 3100,except that entities with DCM beacons are obscured, unless they have apreexisting relationship with the user. It is noted that DCM beacondetection and encryption may operate similarly in wearable computer 3300as in wearable computer 3100, and so substantially duplicated parts havebeen omitted.

Referring again to FIG. 1-R, in an embodiment, wearable computer 3300may include an image capturing module 3310, which may capture an imageof Jules Caesar, who has DCM beacon “A”, Beth Caesar, who has DCM beacon“B”, and Auggie Caesar, who has no DCM beacon. In an embodiment,wearable computer 3300 may include an image acquiring module 3320, whichmay be part of image capturing module 3310, to acquire one or moreimages captured by an image capture device, e.g., the image of JulesCaesar, Beth Caesar, and Auggie Caesar.

In an embodiment, wearable computer 3300 may include an entityidentification module 3330, which may perform one or more recognitionalgorithms on the image in order to identify persons in the image.Entity identification module may use known facial recognitionalgorithms, for example, or may ask the user for input, or may searchthe internet for similar images that have been identified, for example.

Referring again to FIG. 1-R, in an embodiment, wearable computer 3300may include preexisting relationship data retrieval module 3340, whichmay retrieve names of known persons, e.g., from a device contact list,e.g., device contact list 3350. In the example shown in FIG. 1, JulesCaesar is in the contact list of the device 3300. It is noted that thedevice contact list 3350 may be stored on a different device, e.g., theuser's cellular telephone.

Referring now to FIG. 1-Q, in an embodiment, wearable computer 3300 mayinclude data indicating an identified entity from the image data has apreexisting relationship obtaining module 3360, which, in an embodiment,may obtain data indicating that one of the entities recorded in theimage data (e.g., Jules Caesar) is in the user's contact list.

Referring again to FIG. 1-Q, in an embodiment, wearable computer 3300may include entities with preexisting relationship marking to preventobfuscation module 3370. In an embodiment, entities with preexistingrelationship marking to prevent obfuscation module 3370 may attach amarker to the image, e.g., a real marker on the image or a metadataattachment to the image, or another type of marker, that preventsobfuscation of that person, regardless of DCM beacon status, becausethey are in the user's contact list.

Referring again to FIG. 1-Q, in an embodiment, wearable computer 3300may include unknown entities with DCM beacon obscuring module 3380,which may obfuscate any of the entities in the image data that have aDCM beacon and are not in the contact list. For example, in the exampleshown in FIG. 1, Beth Caesar's image is obscured, e.g., blurred, blackedout, covered with advertisements, or the like, because she has a DCMbeacon associated with her image, and because she is not in the user'scontact list. Jules Caesar, on the other hand, is not obscured because aknown entity marker was attached to his image at module 3370, becauseJules Caesar is in the contact list of an associated device of the user.Auggie Caesar is not obscured regardless of contact list status, becausethere is no DCM beacon associated with Auggie Caesar.

Referring again to FIG. 1-Q, after the image is obscured, obscured image3390 of wearable computer 3300 may release the image to the rest of thedevice for processing, or to another device, the Internet, or cloudstorage, for further operations on the image data.

Active DCM Beacon 6000 (FIGS. 1-P and 1-K).

Referring now to FIG. 1-P, in an embodiment, a user 2107 may beassociated with an active DCM beacon 2610, which will be discussed inmore detail herein. The word “Active” in this context merely means thatthe DCM beacon has some form of circuitry or emitter.

Referring now to FIG. 1-K, in an embodiment, the system may include anactive DCM beacon 6000, which may show an active DCM beacon, e.g.,active DCM beacon 2610, in more detail. In an embodiment, beacon 6000may include DCM beacon broadcasting module 6010. In an embodiment, DCMbeacon broadcasting module 6010 may broadcast a privacy beaconassociated with at least one user, e.g., user 2107, from at or near thelocation of user 2107. The beacon may be detected by an image capturingdevice when the user is captured in an image.

Referring again to FIG. 1-K, in an embodiment, the beacon 6000 mayinclude an indication of DCM beacon detection module 6020, which maydetect, be informed of, or otherwise acquire an indication that theactive DCM beacon has been captured by an image capturing device. In anembodiment, indication of DCM beacon detection module 6020 may includeone or more of DCM beacon scanning module 6022, which may scan nearbydevices to see if they have detected the beacon, and DCM beaconcommunications handshake module 6024, which may establish communicationwith one or more nearby devices to determine if they have captured thebeacon.

Referring again to FIG. 1-K, in an embodiment, beacon 6000 may includeterm data broadcasting module 6030, which may broadcast, or which mayorder to be broadcasted, term data, which may include the terms ofservice. In an embodiment, term data broadcasting module 6030 mayinclude one or more of a substantive term data broadcasting module 6032,which may broadcast the actual terms of service, and pointer to termdata broadcasting module 6034, which may broadcast a pointer to theterms of service data that a capturing device may use to retrieve theterms of service from a particular location.

DCM Beacon Test Duplicating Sever 4800 (FIGS. 1-C and 1-D)

Referring now to FIG. 1-C, in an embodiment, the system may include aDCM beacon test duplicating server 4800. In an embodiment, the DCMbeacon test duplicating server 4800 may take the image data, and performthe test for capturing the beacon again, as a redundancy, as averification, or as a protection for wearable computer server 4000. Inan embodiment, DCM beacon test duplicating server 4800 may be a part ofwearable computer server 4000. In another embodiment, DCM beacon testduplicating server 4800 may be separate from wearable computer server4000, and may be controlled by a different entity, e.g., a watchdogentity, or an independent auditing agency.

Referring again to FIG. 1-C, in an embodiment, DCM beacon testduplicating server 4800 may include encrypted data reception forsecondary DCM beacon detection module 4810, which may acquire theencrypted image data containing the user, e.g., user 2105, e.g., JulesCaesar, and the associated DCM beacon, e.g., DCM beacon 2110.

Referring again to FIG. 1-C, in an embodiment, DCM beacon testduplicating server 4800 may include a device-specific key retrievingmodule 4820, which may retrieve the device-specific key, e.g., fromwearable computer device 3100, or from wearable computer server 4000. Inan embodiment, DCM beacon test duplicating server 4800 may include imagedata decryption with device-specific key module 4830, which may applythe device-specific key obtained by device-specific key retrievingmodule 4820, and apply it to the encrypted image data, to generatedecrypted image data.

Referring again to FIG. 1-C, in an embodiment, the unencrypted imagedata may be sent to DCM beacon detecting module 4840 of DCM beacon testduplicating server 4800. If the raw image data was optical in itsoriginal form, then it may be reconverted to optical (e.g., light) data.In an embodiment, DCM beacon detecting module 4840 may perform adetection for the DCM beacon, as previously described. In an embodiment,DCM beacon detecting module 4840 may include one or more of anoptics-based DCM beacon detecting module 4842 and a digital imageprocessing-based DCM beacon detecting module 4844.

Referring now to FIG. 1-D, after the test for detecting the DCM beacon2220 (which may be the same as the DCM beacon 2210, but is detected at adifferent place, so a different number has been assigned), DCM beacondetection at duplicating sever result obtaining module 4850 may obtainthe result of the detection performed at DCM beacon test duplicatingserver 4800. Similarly, DCM beacon detection at device result obtainingmodule 4860 may obtain the result from the DCM beacon detectionperformed at wearable computer device 3100. The results from module 4850and 4860 may be stored at DCM beacon test result storage and loggingmodule 4870 of DCM beacon test duplicating server 4800.

Referring again to FIG. 1-D, the test results from DCM beacon testduplicating server 4800 and from wearable computer 3100 may be stored atDCM beacon test result storage and logging module 4870, and such resultsmay be kept for a predetermined length of time. In an embodiment, theresults may be transmitted to a requesting party using DCM beacon testresult transmitting module 4880.

Referring again to the system, in an embodiment, acomputationally-implemented method may include acquiring an image, saidimage including at least one representation of a feature of at least oneentity, detecting a presence of a privacy beacon associated with the atleast one entity from the acquired image, without performance of afurther process on the acquired image, encrypting the image using aunique device code prior to performance of one or more image processesother than privacy beacon detection, said unique device code unique toan image capture device and not transmitted from the image capturedevice, and facilitating transmission of the encrypted image and privacybeacon data associated with the privacy beacon to a location configuredto perform processing on one or more of the encrypted image and theprivacy beacon data.

Referring again to the system, in an embodiment, acomputationally-implemented method may include acquiring a block ofencrypted data corresponding to one or more images that have previouslybeen encrypted through use of a unique device code associated with animage capture device configured to capture the one or more images,wherein at least one of the one or more images includes at least onerepresentation of a feature of at least one entity, acquiring a privacymetadata, said privacy metadata corresponding to a detection of aprivacy beacon in the one or more images captured by the image capturedevice, said privacy beacon associated with the at least one entity, anddetermining, at least partly based on the obtained privacy metadata, andpartly based on a value calculation based on the representation of thefeature of the at least one entity for which the privacy beacon isassociated, whether to allow processing, which may include distribution,decryption, etc., of the encrypted data block.

Referring again to the system, in an embodiment, acomputationally-implemented method may include acquiring a block ofencrypted data corresponding to one or more images that have previouslybeen encrypted through use of a unique device code associated with animage capture device configured to capture the one or more images,wherein at least one of the one or more images includes at least onerepresentation of a feature of at least one entity, acquiring a privacymetadata indicating detection of a privacy beacon in the one or moreimages captured by the image capture device, said privacy beaconassociated with the at least one entity, retrieving term data from aremote location, said term data corresponding to a term of serviceassociated with a potential release of the block of encrypted datacorresponding to the one or more images that have previously beenencrypted through use of the unique device code associated with theimage capture device configured to capture the one or more images,calculating an expected valuation corresponding to potential revenueassociated with the release of at least a portion of the block ofencrypted data corresponding to the one or more images that havepreviously been encrypted through use of the unique device codeassociated with the image capture device configured to capture the oneor more images, and determining whether to perform decryption of atleast a portion of the block of encrypted data at least partially basedon the calculation of the expected valuation corresponding to thepotential revenue associated with the release of the at least theportion of the block of encrypted data, and at least partially based onthe retrieved term data corresponding to the term of service.

Referring again to the system, in an embodiment, acomputationally-implemented method may include acquiring a block ofencrypted data corresponding to one or more images that have previouslybeen encrypted through use of a unique device code associated with animage capture device configured to capture the one or more images,wherein at least one of the one or more images includes at least onerepresentation of a feature of at least one entity, acquiring a privacymetadata indicating a lack of detection of a privacy beacon in the oneor more images captured by the image capture device, decrypting theblock of encrypted data corresponding to the one or more images thathave previously been encrypted through use of a unique device codeassociated with the image capture device, and encrypting the block ofdecrypted data through use of a unique entity code that is related to anentity associated with the image capture device configured to capturethe one or more images. Referring again to the system, in an embodiment,a computationally-implemented method may include acquiring a block ofencrypted data from a remote location, said block of encrypted datacorresponding to one or more images captured by an image capture device,said block of encrypted data previously encrypted through use of aunique entity code that is related to an entity associated with theimage capture device, receiving an indication that the one or moreimages captured by the image capture device were approved for decryptionthrough a verification related to privacy metadata associated with theone or more images, obtaining the unique entity code related to theentity associated with the image capture device, and releasing the oneor more images through decryption of the block of encrypted dataacquired from the remote location using the obtained unique entity coderelated to the entity associated with the image capture device.

Referring again to the system, in an embodiment, acomputationally-implemented method may include acquiring a block ofencrypted data corresponding to one or more images that have previouslybeen encrypted through use of a unique device code associated with animage capture device configured to capture the one or more images,wherein at least one of the one or more images includes at least onerepresentation of a feature of at least one entity, retrieving term datafrom a remote location, said term data corresponding to a term ofservice associated with a potential release of the one or more imagesthat have previously been encrypted through use of the unique devicecode associated with the image capture device configured to capture theone or more images, calculating whether an estimated advertising revenuefrom one or more advertisement images placed in the one or more imagesof the block of encrypted data will be greater than an estimatedpotential liability for distribution of the one or more images of theblock of encrypted data, said estimated potential liability at leastpartly based on the retrieved term data, modifying the one or moreimages of the block of encrypted data by replacing one or more areasassociated with one or more entities at least partially depicted in theone or more images with the one or more advertisement images, andcalculating a modified estimated advertising revenue from the modifiedone or more images of the block of encrypted data.

Referring again to the system, in an embodiment, acomputationally-implemented method may include monitoring a deploymentof a privacy beacon associated with a user, said privacy beaconconfigured to alert a wearable computer of one or more terms of serviceassociated with said user in response to recordation of image data thatincludes said privacy beacon by said wearable computer, and said privacybeacon configured to instruct said wearable computer to execute one ormore processes to impede transmission of the one or more images thatinclude the user associated with said privacy beacon, and storing arecord of the deployment of the privacy beacon associated with the user,said record configured to be retrieved upon request to confirm whetherthe privacy beacon associated with the user was active at a particulartime.

Referring again to the system, in an embodiment, acomputationally-implemented method may include receiving data regardingone or more features of one or more entities that are designated forprotection by one or more terms of service, associating the one or moreterms of service with a privacy beacon configured to be captured in animage when the one or more features of the one or more entities arecaptured in the image, and providing the terms of service to one or moremedia service providers associated with a device that captured an imagethat includes the privacy beacon, in response to receipt of anindication that an image that includes the privacy beacon has beencaptured.

Referring again to the system, in an embodiment, acomputationally-implemented method may include acquiring one or moreimages that have previously been captured by an image capture device,wherein at least one of the one or more images includes at least onerepresentation of a feature of one or more entities, identifying a firstentity for which at least one representation of a first entity featureis present in the one or more images, and a second entity for which atleast one representation of a second entity feature is present in theone or more images, obtaining data indicating that the first entity hasa preexisting relationship with an entity associated with the imagecapture device, e.g., in a contact list, preventing an obfuscation ofthe representation of the first entity for which the preexistingrelationship with the entity associated with the image capture devicehas been indicated, and obfuscating the representation of the secondentity for which at least one representation of the second entityfeature is present in the one or more images.

Referring again to the system, in an embodiment, acomputationally-implemented method may include broadcasting a privacybeacon associated with at least one entity from a location of the atleast one entity, said privacy beacon configured to be detected by animage capturing device upon capture of an image of the at least oneentity, acquiring an indication that the privacy beacon associated withthe at least one entity has been captured by the image capturing device,and broadcasting term data including one or more conditions and/orconsequences of distribution of one or more images that depict at leasta portion of the at least one entity.

Referring again to the system, in an embodiment, acomputationally-implemented method may include acquiring a block ofencrypted data corresponding to one or more images that have previouslybeen encrypted through use of a unique device code associated with animage capture device configured to capture the one or more images,wherein at least one of the one or more images includes at least onerepresentation of a feature of at least one entity, decrypting the blockof encrypted data corresponding to the one or more images that havepreviously been encrypted through use of the unique device codeassociated with the image capture device configured to capture the oneor more images, performing an operation to detect a presence of aprivacy beacon associated with the at least one entity from the one ormore images, wherein the privacy beacon previously had been detected bythe image capture device, and storing outcome data corresponding anoutcome of the operation to detect the presence of the privacy beaconassociated with the at least one entity of the one or more images,wherein said outcome data includes an indication of whether a result ofthe performed operation to detect the presence of the privacy beaconassociated with the at least one entity from the one or more imagesmatches the previous detection of the privacy beacon by the imagecapture device.

Referring now to FIG. 2, e.g., FIG. 2A, FIG. 2A illustrates an exampleenvironment 200 in which the methods, systems, circuitry, articles ofmanufacture, and computer program products and architecture, inaccordance with various embodiments, may be implemented by one or morebeacon management devices 260. As shown in FIG. 2A, one or morecomputing devices 220 may capture images. For example, computing device220 may capture an image of an entity 105 associated with a privacybeacon, e.g., a DCM (“Don't Capture Me”) beacon 110. In this and someother examples, the captured entity is named “Jules Caesar.”

Referring again to FIG. 2A, computing device 220 may capture the imagedata as image data 22, which may be optical data, e.g., light data,digital data, e.g., a digital signal, or data in another form. In aprocess that will be discussed in more detail herein according tovarious embodiments, image data 22 may be encrypted using adevice-specific code, shown here as encrypted image data 24. Encryptedimage data 24 may be transmitted to a server device 230, which may be anexample of wearable computer server 3000 shown in FIG. 1. In anembodiment, computing device 220 may generate beacon metadata 114 fromthe detected DCM beacon 110. In an embodiment, beacon metadata 114 maybe binary beacon metadata that indicates whether a beacon has beendetected, e.g., yes or no. In an embodiment, beacon metadata 114 mayinclude a data string that identifies the beacon, the entity, the typeof beacon, data about the beacon, or a combination of the foregoing. Inan embodiment, such a beacon metadata 114 may be used by server device230 to obtain additional information about the entity, e.g., terms ofservice data, which will be described in more detail herein. In anembodiment, beacon metadata 114 may include terms of service dataassociated with the entity, e.g., Jules Caesar. The types of beaconmetadata 114 are not limited to those listed in this paragraph, and theforegoing types of beacon metadata 114 will be described in more detailfurther herein with respect to FIGS. 4A-4E, and with respect to thespecific examples listed herein.

Referring again to FIG. 2A, in an embodiment, server device 230 mayinclude an image decryption decision module 236 which may receive theencrypted image 24 and the DCM beacon metadata 114, and determinewhether to allow decryption of the image. This process is described inmore detail with respect to FIGS. 4A-4E, and in previous applications towhich priority is claimed, which have been incorporated herein byreference. A repeating of the operation of server device 230 accordingto various embodiments is omitted here.

Referring again to FIG. 2A, in some embodiments, one or more of theencrypted image data 24 and the DCM beacon metadata are transmitted overone or more communication network(s) 240. In various embodiments, thecommunication network 240 may include one or more of a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a wireless local area network (WLAN), a personal area network(PAN), a Worldwide Interoperability for Microwave Access (WiMAX), publicswitched telephone network (PTSN), a general packet radio service (GPRS)network, a cellular network, and so forth. The communication networks240 may be wired, wireless, or a combination of wired and wirelessnetworks. It is noted that “communication network” as it is used in thisapplication refers to one or more communication networks, which may ormay not interact with each other.

Referring again to FIG. 2A, for example, in an embodiment, environment200 may include a beacon management device 260 Beacon management device260 may be configured to manage associations between one or more privacybeacons, e.g., between DCM beacon 110 and terms of service associatedwith DCM beacon 272. Beacon management device 260 may store, create,modify, update, track, or otherwise manipulate various terms of service.In an embodiment, beacon management device also may store, create,modify, track, communicate with, monitor, or otherwise operate on orwith one or more privacy beacons (e.g., DCM beacon 110) and/or devicesassociated with privacy beacons (e.g., device 109) and/or usersassociated with privacy beacons (e.g., entity 105). In an embodiment,beacon management device 260 may specifically track the detection ofprivacy beacons by various devices, e.g., through communication with oneor more of the aforementioned entities, or through communication with acomputing device 220 and/or a server device 230, as shown in FIG. 2A.Beacon management device 260 may operate on active or passive beacons,as will be discussed in more detail herein. In an embodiment, beaconmanagement device 260 may receive notification of a detected privacybeacon, and provide a terms of service, e.g., terms of service 272, tothe entity that detected the privacy beacon, e.g., server device 230, orcomputing device 220.

Referring again to FIG. 2A, in an embodiment, beacon management device260 may include a service term acquisition module 262. In an embodiment,service term acquisition module 262 may generate terms of service, e.g.,from a predetermined list, or from factors regarding the entityassociated with the privacy beacon, e.g., as will be described in moredetail with respect to specific non-limiting examples herein. In anembodiment, service term acquisition module 262 may receive the terms ofservice, e.g., from a service term generation device 270. Service termgeneration device 270 may be a separate entity that calculates terms ofservice based on various factors, e.g., wealth of the entity, popularityof the entity, the feature that is protected (e.g., private parts maycarry a higher damages base than facial characteristics). In anembodiment, service term generation device 270 may be a part of beaconmanagement device 260. In an embodiment, service term generation device270 may be omitted. Referring now to FIG. 2B, service term acquisitionmodule 262 may include one or more of service term retrieving module262A and service term generation module 262B.

Referring again to FIG. 2A, in an embodiment, beacon management device260 may include an entity monitoring module 264, which may monitor theentity for which the DCM beacon 110 is associated, e.g., entity 105 inFIG. 2A. This monitoring may be used to facilitate the tracking ofdetection of DCM beacon 110, e.g., as described in this and previousapplications, which are incorporated herein by reference. In anembodiment, beacon management device also may include an entitycommunication device module 266, which may be configured to communicatewith a device, e.g., device 109 to facilitate tracking of the privacybeacon, e.g., DCM beacon 110. Device 109 may be related to DCM beacon110, e.g., device 109 may cause DCM beacon 110 to be projected, or, inanother embodiment, device 109 may be unrelated to DCM beacon 110. In anembodiment, device 109 tracks the detection of DCM beacon 110, andinforms beacon management device 260. In an embodiment, device 109 maybe a smartphone device carried by the entity 105.

Referring again to FIG. 2A, in an embodiment, beacon management device260 may include detected beacon communication module 268. Detectedbeacon communication module 268 may be configured to communicate withone or more capture entities, e.g., server device 230 and computingdevice 220. For example, computing device 220 may detect the DCM beacon110, and inform beacon management device 260. Beacon management device260 may then supply the associated terms of service data, e.g., terms ofservice 272, that is associated with DCM beacon 110 to computing device220 and/or server device 230. Similarly, server device 230 may detectDCM beacon 110 and inform beacon management device 260, and receive theassociated terms of service, e.g., terms of service 272. Or, in anotherembodiment, server device 230 may receive a notification from computingdevice 220 that the DCM beacon 110 was detected, and server device 230may then notify beacon management device 260, and receive the associatedterms of service, e.g., terms of service 272. In an embodiment, beaconmanagement device 260 may receive data that identifies the DCM beaconspecifically. In another embodiment, beacon management device 260 mayreceive data that indicates that a particular DCM beacon has beendetected, and may determine which DCM beacon has been detected, andsupply the appropriate terms of service. In an embodiment, if the beaconmanagement device 260 cannot determine which beacon has been detected, adefault terms of service may be supplied to the capture entity.Referring now to FIG. 2B, in an embodiment, detected beaconcommunication module 268 may include one or more of capture devicecommunication module 268A and related device communication module 268B.

Referring again to FIG. 2A, It is noted that, in an embodiment, one ormore of service term acquisition module 262, entity device communicationmodule 266, and entity monitoring module 264, may be part of processor222 shown in FIG. 2B, or may be combined, separated, distributed, and/oromitted in other combinations not specifically enumerated here.

Referring again to FIG. 2A, in some embodiments, one or more of theencrypted beacon data and the terms of service data may be transmittedthrough use of communication network(s) 240. In various embodiments, thecommunication network 240 may include one or more of a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a wireless local area network (WLAN), a personal area network(PAN), a Worldwide Interoperability for Microwave Access (WiMAX), publicswitched telephone network (PTSN), a general packet radio service (GPRS)network, a cellular network, and so forth. The communication networks240 may be wired, wireless, or a combination of wired and wirelessnetworks. It is noted that “communication network” as it is used in thisapplication refers to one or more communication networks, which may ormay not interact with each other.

Referring again to FIG. 2A, computing device 220 may be any electronicdevice, portable or not, that may be operated by or associated with oneor more users. Computing device 220 is shown as interacting with a user115. As set forth above, user 115 may be a person, or a group of people,or another entity that mimics the operations of a user. In anembodiment, user 115 may be a computer or a computer-controlled device.Computing device 220 may be, but is not limited to, a wearable computer.Computing device 220 may be any device that is equipped with an imagecapturing component, including, but not limited to, a cellular phone, anetwork phone, a smartphone, a tablet, a music player, a walkie-talkie,a radio, an augmented reality device (e.g., augmented reality glassesand/or headphones), wearable electronics, e.g., watches, belts,earphones, or “smart” clothing, earphones, headphones, audio/visualequipment, media player, television, projection screen, flat screen,monitor, clock, appliance (e.g., microwave, convection oven, stove,refrigerator, freezer), a navigation system (e.g., a Global PositioningSystem (“GPS”) system), a medical alert device, a remote control, aperipheral, an electronic safe, an electronic lock, an electronicsecurity system, a video camera, a personal video recorder, a personalaudio recorder, and the like.

Referring now to FIG. 2B, FIG. 2B shows a detailed description of abeacon management device 260 operating in environment 200, in anembodiment. It is noted that the components shown in FIG. 2B representmerely one embodiment of beacon management device 260, and any or allcomponents other than processor 222 may be omitted, substituted, ormodified, in various embodiments.

Referring again to FIG. 2B, beacon management device 260 may include adevice memory 245. In an embodiment, device memory 245 may includememory, random access memory (“RAM”), read only memory (“ROM”), flashmemory, hard drives, disk-based media, disc-based media, magneticstorage, optical storage, volatile memory, nonvolatile memory, and anycombination thereof. In an embodiment, device memory 245 may beseparated from the device, e.g., available on a different device on anetwork, or over the air. For example, in a networked system, there maybe many beacon management devices 260 whose device memory 245 is locatedat a central server that may be a few feet away or located across anocean. In an embodiment, beacon management device 260 may include adevice memory 245. In an embodiment, memory 245 may comprise of one ormore of one or more mass storage devices, read-only memory (ROM),programmable read-only memory (PROM), erasable programmable read-onlymemory (EPROM), cache memory such as random access memory (RAM), flashmemory, synchronous random access memory (SRAM), dynamic random accessmemory (DRAM), and/or other types of memory devices. In an embodiment,memory 245 may be located at a single network site. In an embodiment,memory 245 may be located at multiple network sites, including sitesthat are distant from each other.

Referring again to FIG. 2B, beacon management device 260 may include oneor more of device memory 245, service term acquisition module 262,entity communication module 264, entity device communication module 266,and detected beacon communication module 268. FIG. 2B further shows amore detailed description of beacon management device 260. In anembodiment, beacon management device 260 may include a processor 222.Processor 222 may include one or more microprocessors, CentralProcessing Units (“CPU”), a Graphics Processing Units (“GPU”), PhysicsProcessing Units, Digital Signal Processors, Network Processors,Floating Point Processors, and the like. In an embodiment, processor 222may be a server. In an embodiment, processor 222 may be adistributed-core processor. Although processor 222 is as a singleprocessor that is part of a single beacon management device 260,processor 222 may be multiple processors distributed over one or manybeacon management devices 260, which may or may not be configured tooperate together.

Processor 222 is illustrated as being configured to execute computerreadable instructions in order to execute one or more operationsdescribed above, and as illustrated in FIGS. 9, 10A-10C, 11A-11F, and12A-12D. In an embodiment, processor 222 is designed to be configured tooperate as processing module 250, which may include one or more ofentity data that is related to at least one feature of an entity that isconfigured to be assigned for coverage by one or more terms of serviceobtaining module 252, association of the one or more terms of servicewith a privacy beacon that is configured to be detected when the atleast one feature of the entity is captured in a captured imagefacilitating module 254, and associated one or more terms of serviceproviding to a capture entity associated with a device that possessesthe captured image in response to an indication that the privacy beaconhas been detected module 256.

FIGS. 3A-3E refer to an “image capture device,” which is defined as anydevice that is equipped with the ability to capture images, and notnecessarily a wearable computer or a device designed specifically tocapture images.

Referring now to FIG. 3A, FIG. 3A shows an exemplary embodiment of acomputing device 220 as image capture device 302. In an embodiment,image capture device 302 may include an image capture component, e.g., alens 306A. Image capture component 306A may capture an image includingthe user 105 and the DCM beacon 110, and capture that image as raw(optical or digital) data 120. In an embodiment, image capture device302 may include beacon detection module 310A that is configured todetect DCM beacon 110, either optically, digitally, or other, dependingon the embodiment. After detection of the beacon, the image data may besent to an image data encryption module 320A to encrypt the image. In anembodiment, if the beacon is not detected, the image data 120 isreleased past barrier 340A and the other image capture device modules350A may operate on the image data 120. In an embodiment, the encrypteddata, and data associated with the DCM beacon 110 (although notnecessarily the beacon itself) may be transmitted to encrypted data andbeacon transmitting module 330A, which may transmit the encrypted dataand beacon data to an external source, e.g., server 3000 as described inFIG. 1. It is noted that beacon detection module 310A, image dataencryption module 320A, and encrypted data and beacon transmittingmodule 330A may be separated from other image capture device modules350A by barrier 340A.

In an embodiment, barrier 340A may be a physical barrier, e.g., beacondetection module 310A, lens 306A, image data encryption module 320A, andencrypted data and beacon transmitting module 330A may be hard-wired toeach other and electrically excluded from other image capture devicemodules 350A. In another embodiment, barrier 340A may be implemented asa programmed barrier, e.g., the image data 120 is not transmitted tomodules other than beacon detection module 310A, lens 306A, image dataencryption module 320A, and encrypted data and beacon transmittingmodule 330A. In another embodiment, barrier 340A may be implemented as adata access barrier, e.g., the captured image data 120 may be protected,e.g., with an access or clearance level, so that only beacon detectionmodule 310A, lens 306A, image data encryption module 320A, and encrypteddata and beacon transmitting module 330A may read or operate on theimage data 120. In another embodiment, barrier 340A may not be acomplete barrier, e.g., barrier 340A may allow “read” access to theimage data, but not “copy” or “write” access. In another embodiment,barrier 340A may be a barrier to transmission, e.g., the image may beviewed locally at the device, but may be barred from being saved to aremovable memory, or uploaded to a cloud storage or social networkingsite/social media site.

Referring now to FIG. 3B, FIG. 3B shows an embodiment of a computingdevice 220 as image capture device 304. In an embodiment, image capturedevice 304 may include an image capture component, e.g., a lens andsensor 306B. Image capture component 306B may capture an image includingthe user 105 and the DCM beacon 110, and capture that image as raw(optical or digital) data 120. In an embodiment, image capture device304 may include image path splitting module 305B that may receive theraw data 120 as a signal, e.g., optical or digital, and split the signalinto two branches. As shown in FIG. 3B, one branch, e.g., the northbranch, sends the raw signal to image data encryption module 320B, whichmay encrypt the image. In an embodiment, the other branch, e.g., thesouth branch, may send the signal to a beacon detection module 310B,which may detect the DCM beacon 110. In an embodiment, if the DCM beacon110 is detected, then the unencrypted image data that arrived at beacondetection module 310B is destroyed. In an embodiment, if the DCM beacon110 is not detected, then the encrypted image data from image dataencryption module 320B is destroyed, and the unencrypted image data atbeacon detection module 310B is allowed to pass to other image capturedevice modules 350B. In an embodiment, the beacon detection result andthe encrypted image data are transmitted to the encrypted data andbeacon transmitting module 330B. In an embodiment, barrier 340B mayseparate image path splitting module 305B, beacon detection module 310B,image data encryption module 320B, and encrypted data and beacontransmitting module 330B from other image capture device modules 350B.

In an embodiment, barrier 340B may be a physical barrier, e.g., beacondetection module 310B, lens 306B, image data encryption module 320B, andencrypted data and beacon transmitting module 330B may be hard-wired toeach other and electrically excluded from other image capture devicemodules 350B. In another embodiment, barrier 340B may be implemented asa programmed barrier, e.g., the image data 120 is not transmitted tomodules other than image path splitting module 305B, beacon detectionmodule 310B, lens 306B, image data encryption module 320B, and encrypteddata and beacon transmitting module 330B. In another embodiment, barrier340B may be implemented as a data access barrier, e.g., the capturedimage data may be protected, e.g., with an access or clearance level, sothat only beacon detection module 310B, lens 306B, image data encryptionmodule 320B, and encrypted data and beacon transmitting module 330B mayread or operate on the image data 120. In another embodiment, barrier340B may not be a complete barrier, e.g., barrier 340B may allow “read”access to the image data, but not “copy” or “write” access. In anotherembodiment, barrier 340B may be a barrier to transmission, e.g., theimage may be viewed locally at the device, but may be barred from beingsaved to a removable memory, or uploaded to a cloud storage or socialnetworking site/social media site.

Referring now to FIG. 3C, FIG. 3C shows an embodiment of a computingdevice 220 implemented as image capture device 306. In an embodiment,image capture device 306 may include an image capture component 306Cthat captures optical data 120A. In an embodiment, optical data 120A maybe sent to optical splitting module 305C, which may split the opticalsignal, e.g., the light, into two paths. Referring to FIG. 3C, the“south” path may transmit the light to an optical filter 312, which mayfilter the light for a specific characteristic, e.g., a wavelength or anobject, according to known optical filtration techniques. In anembodiment, the filtered optical signal may then be transmitted to afiltered optical signal beacon detection module 310C, which may detectthe beacon 110 in the optical data 120A.

Referring again to FIG. 3C, the “north” path from optical splittingmodule 305C may transmit the optical image data to an optical-to-digitalconverter 314, e.g., a CMOS or CCD sensor. In an embodiment, the digitalsignal then may be transmitted to image data encryption module 320C, andthe encrypted data transmitted to encrypted data and beacon transmittingmodule 330C, along with the beacon detection result, for transmission toan external source, e.g., server 3000 as shown in FIG. 1. In anembodiment, barrier 340C may prevent access to the unencrypted imagedata by other image capture device modules 350C. In an embodiment,barrier 340C may function similarly to barriers 340A and 340B, and thedescriptions of those barriers and their possible implementations alsomay apply to barrier 340C. In an embodiment, image data encryptionmodule 320C, encrypted data beacon and transmitting module 330C, andoptical-to-digital converter 314 may be controlled by beacon detectioncontrol module 325, which may be part of the processor of image capturedevice 306C, or may be a separate processor. In an embodiment, beacondetection control module 325 may form part or all of processor 222 ofcomputing device 220 of FIG. 2B.

Referring now to FIG. 3D, FIG. 3D shows an exemplary implementation of acomputing device 220 implemented as image capture device 308, accordingto an embodiment. Image capture device 308 may include an optical imagecollector 306D that may capture an image including the user 105 and theDCM beacon 110, and capture that image as optical data 120A. Opticaldata 120A may then be sent to optical splitting module 305D, which maysplit the optical signal, e.g., the light, into two paths. Referring toFIG. 3D, the “south” path may transmit the light to an opticaltransformation module 332, which may apply a transformation, e.g., aFourier transformation, to the optical image data. The transformedoptical data from module 332, as well as a reference image from opticalbeacon reference signal providing module 334 may be transmitted tooptical beacon detection module 310D. Optical beacon detection module310D may optically detect the beacon using Fourier transformation and anoptical correlator. The basic operation of performing optical imageobject detection is described in the publically-available (at theUniversity of Michigan Online Library) paper “Report of ProjectMICHIGAN, SIGNAL DETECTION BY COMPLEX SPATIAL FILTERING,” by A. B.Vander Lugt, printed in July 1963 at the Radar Laboratory at theInstitute of Science and Technology, the University of Michigan, whichis hereby incorporated by reference in its entirety. Applicant'srepresentative is including a copy of this paper with the filing of thisapplication, for the convenience of the Examiner.

Referring again to FIG. 3D, the “north” path from optical splittingmodule 305D may transmit the optical image data to an optical-to-digitalconverter 324, e.g., a CMOS or CCD sensor. In an embodiment, the digitalsignal then may be transmitted to image data encryption module 320D, andthe encrypted data transmitted to encrypted data and beacon transmittingmodule 330D, along with the beacon detection result, for transmission toan external source, e.g., server 3000 as shown in FIG. 1. In anembodiment, barrier 340D may prevent access to the unencrypted imagedata by other image capture device modules 350D. In an embodiment,barrier 340D may function similarly to barriers 340A and 340B, and thedescriptions of those barriers and their possible implementations alsomay apply to barrier 340D. In an embodiment, image data encryptionmodule 320D, encrypted data and beacon transmitting module 330D, andoptical-to-digital converter 324 may be controlled by beacon detectioncontrol module 335, which may be part of the processor of image capturedevice 308, or may be a separate processor. In an embodiment, beacondetection control module 335 may form part or all of processor 222 ofcomputing device 220 of FIG. 2B.

Referring now to FIG. 3E, FIG. 3E shows an exemplary embodiment of animplementation of computing device 220 as image capture device 309. Inan embodiment, image capture device 309 may include an optical imagecollector 306E, e.g., a lens, which may collect the optical data 120A.Optical data 120A may be emitted to an optical beacon detection module310E, which may detect the DCM beacon 110 using one of theabove-described optical detection methods. After detection of the beaconusing optical techniques, the optical signal may be captured by anoptical-to-digital conversion module 344, and converted to digital imagedata, which is transferred to image data encryption module 320E forencryption. In an embodiment, modules 306E, 310E, 344, and 320E, arehard-wired to each other, and separated from encrypted data and beacontransmitting module 330E and other image capture device modules 350E bybarrier 340E (which, in this embodiment, is shown for exemplary purposesonly, because the physical construction of modules 306E, 310E, 344, and320E removes the need for a barrier 340E, whether implemented ashardware, programming, security, or access. In this embodiment, theimage data is encrypted prior to interaction with the “main” portions ofimage capture device 309, and after the beacon data has been opticallydetected.

FIGS. 4A-4E show one or more embodiments of a server device 230,according to one or more embodiments. Unless otherwise stated orcontradictory to FIGS. 4A-4E, the server devices 430A, 430B, 430C, 430D,and 430E may include the elements of server device 230, as previouslydescribed. Similarly, unless otherwise stated or contradictory to FIGS.4A-4E, the computing devices 420A, 420B, 420C, 420D, and 420E mayinclude the elements of computing device 220, as previously described.

Referring now to FIG. 4A, FIG. 4A shows an exemplary implementation ofserver device 230 as server device 430A operating in exemplaryenvironment 400A. In an embodiment, computing device 420A furtherincludes a location and time log and transmission module 422. In anembodiment, location and time log and transmission module 422 may recorda location, e.g., through global positioning sensors, triangulationusing radio signals, or other methods, of the computing device 420A, anda time that the image is captured, at the time the image is captured.This data of location and time of the image capture, e.g., location andtime of detection data 162, may be transmitted to server device 430A, asshown in FIG. 4A.

Referring again to FIG. 4A, server device 430A may include a beaconmetadata acquisition module 433. Beacon metadata acquisition module 433may include location and time of beacon detection data acquisitionmodule 433A. Location and time of beacon detection data acquisitionmodule 433A may receive the location and time of detection data 162. Inan embodiment in which the beacon metadata 150 is binary beacon metadata150A, additional data regarding the image may be obtained. For example,server device 430A may transmit the location and time of detection data162 to a remote location, e.g., to beacon support server 490. Beaconsupport server 490 may include, for example, a geotagged and timestampedlist of detected beacons 436, which may track a location and time when abeacon is detected. Beacon support server 490 may be associated with DCMbeacon 110, and may be configured to log each time DCM beacon 110 isdetected, e.g., in an embodiment in which DCM beacon 110 is an activebeacon that can determine when it is detected. In an embodiment, beaconsupport server 490 may use the location and time of detection data 162to determine which DCM beacon 110 is detected, and transmit the beaconidentification information back to server device 430A, e.g., to beaconidentification data acquisition module 433B. In an embodiment, thisbeacon identification information may be used by server device 430A. Inan embodiment, the beacon identification information may be used toidentify the entity in the image, without decrypting the image, forexample.

Referring now to FIG. 4B, FIG. 4B shows an exemplary implementation ofserver device 230 as server device 430B operating in exemplaryenvironment 400B. In an embodiment, the computing device 420B maygenerate beacon metadata 150, which may be binary beacon metadata 150A,and transmit the binary beacon metadata 150A to server device 430B. Inan embodiment, server device 430B receives the binary beacon metadata150A, e.g., through use of beacon metadata acquisition module 443, whichmay describe whether a beacon was detected in the encrypted image datablock 160, but which may, in an embodiment, not provide additional dataregarding the beacon. In an embodiment, server device 430B may includeencrypted image analysis and data extraction module 442, which mayperform analysis on the encrypted image 24, if possible. Such analysismay include, for example, that the encrypted image data block 160 mayhave metadata that is not encrypted or that may be read through theencryption. In an embodiment, for example, the image 22 may be encryptedin such a manner that certain characteristics of the encrypted image 24may be obtained without decrypting the image. In an embodiment, serverdevice 430B may use encrypted image analysis and data extraction module442 to determine more information about the image, e.g., which may beused to perform valuation of the image and/or to retrieve term dataregarding one or more terms of service associated with the DCM beacon110 and the entity Jules Caesar 105.

Referring now to FIG. 4C, FIG. 4C shows an exemplary implementation ofserver device 230 as server device 430C operating in exemplaryenvironment 400C. In an embodiment, computing device 420C may transmitthe beacon metadata 150, which may be binary beacon metadata 150A, toserver device 430C. Beacon metadata 150 may be obtained by beaconmetadata acquisition module 456. In an embodiment, beacon metadataacquisition module 456 may relay data regarding the received metadata toa decision-making portion of server device 430C, e.g., a centralprocessor. In an embodiment, server device 430C may determine that itwants more data regarding the image 22, in order to retrieve term data,or perform a valuation of the image data. Accordingly, in an embodiment,server device 430C may include encrypted image analysis and dataextraction module 436, which may operate similarly to encrypted imageanalysis and data extraction module 442, and also, in an embodiment,encrypted image analysis and data extraction module 436 may transmit theencrypted image data block to a “sandbox,” e.g., image decryptionsandbox 492. Image decryption sandbox 492 may place the image in avirtual or physical “sandbox” where other processes may be unable toaccess the data. Image decryption sandbox 492 may be part of serverdevice 430C, or may be a separate entity. In an embodiment, imagedecryption sandbox 492 may decrypt the encrypted image 24. Encryptedimage decryption and beacon identification module 493 may performanalysis on the decrypted image, including identifying the beacon, oridentifying the entity, or a combination thereof. The identificationdata then may be given to beacon identification data reception module438. In an embodiment, the decrypted image data is then trapped in thesandbox and/or destroyed.

Referring now to FIG. 4D, FIG. 4D shows an exemplary implementation ofserver device 230 as server device 430D operating in exemplaryenvironment 400D. In an embodiment, computing device 420D may transmitbeacon metadata 150, e.g., beacon identifier metadata 150B, to serverdevice 430D. In an embodiment, beacon identifier metadata 150B mayidentify the beacon, e.g., the DCM beacon 110. The identification may bea unique identification, e.g. “this beacon is associated with user#13606116, Jules Caesar,” or, in an embodiment, the identification maybe a class of beacon, e.g., “this is a beacon with a $100,000 dollarliquidated damages clause associated with using a likeness of the entityassociated with the beacon,” or “this is a beacon of a televisioncelebrity,” or “this is a beacon provided by Image Protect Corporation.”

Referring again to FIG. 4D, server device 430D receives the beaconidentifier metadata 150B, e.g., through use of beacon metadataacquisition module 447. In an embodiment, server device 430D maytransmit the identifier to an external location, e.g., a terms ofservice transmission server 485. Terms of service transmission server485 may store terms of service associated with various beacons in itsterms of service repository 489. In an embodiment, each unique beaconmay be associated with its own unique terms of service. In anotherembodiment, there may be common terms of service for various users. Inanother embodiment, there may be common terms of service for variousclasses of users. In an embodiment, the terms of service may varydepending on how much the entity, e.g., Jules Caesar, is paying to usethe beacon service.

In an embodiment, terms of service transmission server 485 may includebeacon identifier lookup table 487. Beacon identifier lookup table 487may receive the beacon identifier metadata 150B, and use the beaconidentifier metadata 150B to obtain the terms of service associated withthat beacon, e.g., terms of service data 151. In an embodiment, terms ofservice data 151 then may be transmitted to server device 430D.

Referring now to FIG. 4E, FIG. 4E shows an exemplary implementation ofserver device 230 as server device 430E operating in exemplaryenvironment 400E. In an embodiment, computing device 420E may detect theDCM beacon 110, and may obtain the terms of service from the detectedbeacon (e.g., the terms of service may be read from the beacon, e.g., incompressed binary). In an embodiment, the computing device 420E may usethe detected beacon data to obtain the terms of service data fromanother location, e.g., a terms of service data server (not pictured).

Referring again to FIG. 4E, in an embodiment, computing device 420E maytransmit beacon metadata 150, e.g., beacon identifier and terms ofservice metadata 150C, to server device 430E. Beacon metadataacquisition module 444 may receive the beacon identifier and terms ofservice metadata 150C, and detect that the terms of service are presentin the beacon metadata 150. In an embodiment, beacon metadata terms ofservice reading module 454 may read the terms of service from the beaconmetadata 150.

The foregoing examples are merely provided as examples of how beacondata may operate, and how identifying data and/or term of service datamay be obtained by the various server devices, and should not beinterpreted as limiting the scope of the invention, which is definedsolely by the claims. Any and all components of FIGS. 4A-4E may becombined with each other, modified, or eliminated.

FIGS. 5A-5D show one or more embodiments of a computing device 230,among other components, operating in an environment 500 (e.g.,500A-500D), according to one or more embodiments. Unless otherwisestated or contradictory to FIGS. 5A-5D, the server devices 530A, 530B,530C, and 530D may include the elements of server device 230, aspreviously described. Similarly, unless otherwise stated orcontradictory to FIGS. 5A-5D, the computing devices 520A, 520B, 520C,and 520D may include the elements of computing device 220, as previouslydescribed.

Referring now to FIG. 5A, FIG. 5A shows an exemplary implementation ofserver device 230 as server device 530A operating in exemplaryenvironment 500A. In an embodiment, as shown in FIG. 5A, computingdevice 520A may capture an image that includes an entity 105 that may beassociated with a privacy beacon, e.g., DCM beacon 110. In anembodiment, the captured image, e.g., image 22, may be encrypted intoencrypted image 24 using a device-based encryption key. In anembodiment, encrypted image 24 may be combined with beacon metadata,e.g., beacon metadata 150, in an encrypted image data block 160. Inanother embodiment, beacon metadata 150 may be separate from encryptedimage data block 160. In an embodiment, the encrypted image 24 may betransmitted to a server device 530A by encrypted image data transmittingmodule 180. In an embodiment, a decryption determination module 532A maydetermine to decrypt the image, e.g., in a process described in one ormore of this and/or previous applications incorporated by reference. Inan embodiment, server device 530A may include decryption module 534A,which may apply a device-based decryption key to the encrypted image 24to generate decrypted image data. In an embodiment, client-basedencryption module 536A may apply a client-based encryption key to thedecrypted image data, to generate a client-based encrypted image. In anembodiment, the client-based encrypted image then may be transmittedback to the computing device 520A, which may be a wearable computer,e.g., to client-based encrypted data receiving module 190. In anembodiment, upon receipt of the client-based encrypted image theclient-based encrypted image decryption module 195 may decrypt theclient-based encrypted image.

In an embodiment, one or more of the originally-captured image 22, thedecrypted image data in the decryption module 534A of server device530A, and the decrypted image data in the client-based encryption module536A may be identical. In another embodiment, the substantive portion ofthe data (e.g., the color data) may be identical, and other data, e.g.,header data or compression data, may be different. In anotherembodiment, the decrypted image data in the decryption module 534A ofserver device 530A, and the decrypted image data in the client-basedencryption module 536A may be slightly different.

Referring now to FIG. 5B, FIG. 5B shows an exemplary implementation ofserver device 230 as server device 530B operating in exemplaryenvironment 500B. In an embodiment, as shown in FIG. 5B, computingdevice 520B may capture an image that includes an entity 105 that may beassociated with a privacy beacon, e.g., DCM beacon 110. In anembodiment, the captured image, e.g., image 22, may be encrypted intoencrypted image 24 using a device-based encryption key. In anembodiment, encrypted image 24 may be combined with beacon metadata,e.g., beacon metadata 150, in an encrypted image data block 160. Inanother embodiment, beacon metadata 150 may be separate from encryptedimage data block 160. In an embodiment, the encrypted image 24 may betransmitted to a server device 530B by encrypted image data transmittingmodule 180. In an embodiment, a decryption determination module 532B maydetermine to decrypt the image, e.g., in a process described in one ormore of this and/or previous applications incorporated by reference. Inan embodiment, server device 530B may include decryption module 534B,which may apply a device-based decryption key to the encrypted image 24to generate decrypted image data. In an embodiment, client-basedencryption module 536B may apply a client-based encryption key to thedecrypted image data, to generate a client-based encrypted image.

Referring again to FIG. 5B, in an embodiment, the client-based encryptedimage then may be transmitted to a device that is not the computingdevice 520B, e.g., rather to other client-associated computer device550. Other client-associated computer device 550 may includeclient-based encrypted data receiving module 191 and/or client-basedencrypted image decryption module 194 which may decrypt the client-basedencrypted image, similarly to modules 190 and 195 of FIG. 5A, but notpart of computing device 520B. In an embodiment, computer device 550 mayalso be worn or carried by the client, e.g., a smartphone carried by theclient that was wearing the wearable computer 520B. In an embodiment,computer device 550 may be remote from the client, e.g., the client'shome computer. In another embodiment, computer device 550 may be ashared server, e.g., where the client stores images on the cloud. In anembodiment similar to the one described above, the computing device 520Bmay not possess the decrypted image at any point during the process.

Referring again to FIG. 5B, similarly to FIG. 5A, in an embodiment, oneor more of the originally-captured image 22, the decrypted image data inthe decryption module 534B of server device 530B, and the decryptedimage data in the client-based encryption module 536B may be identical.In another embodiment, the substantive portion of the data (e.g., thecolor data) may be identical, and other data, e.g., header data orcompression data, may be different. In another embodiment, the decryptedimage data in the decryption module 534B of server device 530B, and thedecrypted image data in the client-based encryption module 536B may beslightly different.

Referring now to FIG. 5C, FIG. 5C shows an exemplary implementation ofserver device 230 as server device 530C operating in exemplaryenvironment 500C. In an embodiment, as shown in FIG. 5C, computingdevice 520C may capture an image that includes an entity 105 that may beassociated with a privacy beacon, e.g., DCM beacon 110. In anembodiment, the captured image, e.g., image 22, may be encrypted intoencrypted image 24 using a device-based encryption key. In anembodiment, encrypted image 24 may be combined with beacon metadata,e.g., beacon metadata 150, in an encrypted image data block 160. Inanother embodiment, beacon metadata 150 may be separate from encryptedimage data block 160. In an embodiment, the encrypted image 24 may betransmitted to a server device 530C by encrypted image data transmittingmodule 180. In an embodiment, a decryption determination module 532C maydetermine to decrypt the image, e.g., in a process described in one ormore of this and/or previous applications incorporated by reference.

Referring again to FIG. 5C, in an embodiment, one or more of thedecision to decrypt the encrypted image 24, and the encrypted image 24may be transmitted to a client-based encryption handling device 560. Inan embodiment, client-based encryption handling device 560 may includedecryption module 562, which may apply a device-based decryption key tothe encrypted image 24 to generate decrypted image data. In anembodiment, client-based encryption module 564 may apply a client-basedencryption key to the decrypted image data, to generate a client-basedencrypted image. In an embodiment, the client-based encrypted image,then may be transmitted back to the computing device 520A, which may bea wearable computer, e.g., to client-based encrypted data receivingmodule 190. In an embodiment, upon receipt of the client-based encryptedimage the client-based encrypted image decryption module 195 may decryptthe client-based encrypted image.

Referring again to FIG. 5C, similarly to FIG. 5A, in an embodiment, oneor more of the originally-captured image 22, the decrypted image data inthe decryption module 562 of client-based encryption handling device560, and the decrypted image data in the client-based encryption module564 may be identical. In another embodiment, the substantive portion ofthe data (e.g., the color data) may be identical, and other data, e.g.,header data or compression data, may be different. In anotherembodiment, the decrypted image data in the decryption module 562 ofclient-based encryption handling device 560, and the decrypted imagedata in the client-based encryption module 564 may be slightlydifferent.

Referring now to FIG. 5D, FIG. 5D shows an exemplary implementation ofserver device 230 as server device 530D operating in exemplaryenvironment 500D. In an embodiment, as shown in FIG. 5D, computingdevice 520D may capture an image that includes an entity 105 that may beassociated with a privacy beacon, e.g., DCM beacon 110. In anembodiment, the captured image, e.g., image 22, may be encrypted intoencrypted image 24 using a device-based encryption key. In anembodiment, encrypted image 24 may be combined with beacon metadata,e.g., beacon metadata 150, in an encrypted image data block 160. Inanother embodiment, beacon metadata 150 may be separate from encryptedimage data block 160. In an embodiment, the encrypted image 24 may betransmitted to a server device 530D by encrypted image data transmittingmodule 180. In an embodiment, a decryption determination module 532D maydetermine to decrypt the image, e.g., in a process described in one ormore of this and/or previous applications incorporated by reference. Inan embodiment, server device 530D may include decryption module 534D,which may apply a device-based decryption key to the encrypted image 24to generate decrypted image data. In an embodiment, client-basedencryption module 536D may apply a client-based encryption key to thedecrypted image data, to generate a client-based encrypted image.

Referring again to FIG. 5D, in an embodiment, the client-based encryptedimage then may be transmitted to a device that is not the computingdevice 520D, e.g., rather to a social networking server 570 or filerepository 570. In an embodiment, social networking server 570 mayinclude client-based encrypted data receiving module 192, similarly toclient-based encrypted data receiving module 190 of FIG. 5A. In anembodiment, social networking server 570 may include the client-basedencrypted image decryption module 197, which may be similar to theclient-based encrypted image decryption module 195 of FIG. 5A, and whichmay decrypt the client-based encrypted image. In an embodiment, socialnetworking server 570 may automatically decrypt the image, and/or takeone or more actions, e.g., posting the image to a user's account, e.g.,their “wall” on Facebook, or a similar structure. In another embodiment,the social networking server 570 may wait to decrypt the image, and/orto take one or more actions with the image, until the client thatcaptured the image logs into the social networking service associatedwith the social networking server 570.

Referring again to FIG. 5D, similarly to FIG. 5A, in an embodiment, oneor more of the originally-captured image 22, the decrypted image data inthe decryption module 534D of server device 530D, and the decryptedimage data in the client-based encryption module 536D may be identical.In another embodiment, the substantive portion of the data (e.g., thecolor data) may be identical, and other data, e.g., header data orcompression data, may be different. In another embodiment, the decryptedimage data in the decryption module 534D of server device 530D, and thedecrypted image data in the client-based encryption module 536D may beslightly different.

Referring now to FIG. 6, FIG. 6 illustrates an exemplary implementationof the entity data that is related to at least one feature of an entitythat is configured to be assigned for coverage by one or more terms ofservice obtaining module 252. As illustrated in FIG. 6, the entity datathat is related to at least one feature of an entity that is configuredto be assigned for coverage by one or more terms of service obtainingmodule may include one or more sub-logic modules in various alternativeimplementations and embodiments. For example, as shown in FIG. 6, e.g.,FIG. 6A, in an embodiment, module 252 may include one or more of entityimage data that includes a photographic depiction of the at least onefeature of the entity that is configured to be assigned for coverage byone or more terms of service obtaining module 602, three-dimensionalhead model data of a head of the entity that is configured to beassigned for coverage by one or more terms of service obtaining module612, and set of feature coordinates that describe at least one featureof the entity that is configured to be assigned for coverage by one ormore terms of service obtaining module 614. In an embodiment, module 602may include one or more of entity image data that includes aphotographic depiction of a face of the entity that is configured to beassigned for coverage by one or more terms of service obtaining module604 and entity image data that includes a photographic depiction of abody part of the entity that is configured to be assigned for coverageby one or more terms of service obtaining module 608. In an embodiment,module 604 may include entity image data that includes a multipledepictions of a face of the entity from one or more angles, the faceconfigured to be assigned for coverage by one or more terms of serviceobtaining module 606. In an embodiment, module 608 may include entityimage data that includes a photographic depiction of an entire body ofthe entity that is configured to be assigned for coverage by one or moreterms of service obtaining module 610.

Referring again to FIG. 6, e.g., FIG. 6B, in an embodiment, module 252may include entity data that is related to at least one feature of theentity that is configured to be assigned for coverage by the one or moreterms of service that govern one or more images that depict the at leastone feature of the entity obtaining module 616. In an embodiment, module616 may include one or more of entity data that is related to at leastone feature of the entity that is configured to be assigned for coverageby the one or more terms of service that set one or more conditions thatare applicable to one or more images that depict the at least onefeature of the entity obtaining module 618 and entity data that isrelated to at least one feature of the entity that is configured to beassigned for coverage by the one or more terms of service that govern ause of the one or more images that depict the at least one feature ofthe entity obtaining module 620. In an embodiment, module 620 mayinclude one or more of entity data that is related to at least onefeature of the entity that is configured to be assigned for coverage bythe one or more terms of service that govern an unauthorized use of oneor more surreptitiously captured images that depict the at least onefeature of the entity obtaining module 622 and entity data that isrelated to at least one feature of the entity that is configured to beassigned for coverage by the one or more terms of service that govern adistribution of the one or more images that depict the at least onefeature of the entity obtaining module 626. In an embodiment, module 622may include entity data that is related to at least one feature of theentity that is configured to be assigned for coverage by the one or moreterms of service that govern an unauthorized use of one or more wearablecomputer captured surreptitious images that depict the at least onefeature of the entity obtaining module 624.

Referring again to FIG. 6, e.g., FIG. 6C, in an embodiment, module 252may include one or more of entity data that includes a list of the atleast one feature of an entity that is configured to be assigned forcoverage by one or more terms of service obtaining module 628, entitydata that includes a description of the at least one feature of anentity that is configured to be assigned for coverage by one or moreterms of service obtaining module 630, entity data that is related to atleast one feature of the entity that is configured to be assigned forcoverage by one or more terms of service that take effect uponacquisition of the at least one feature of the entity in an imageobtaining module 632, and entity data that is related to at least onefeature of the entity that is configured to be assigned for coverage byone or more terms of service that specify a damages for use of an imagethat depicts the at least one feature of the entity obtaining module634. In an embodiment, module 634 may include one or more of entity datathat is related to at least one feature of the entity that is configuredto be assigned for coverage by one or more terms of service that specifythe damages for a sale of the image that depicts the at least onefeature of the entity obtaining module 636 and entity data that isrelated to at least one feature of the entity that is configured to beassigned for coverage by one or more terms of service that specify thedamages for a distribution of the image that depicts the at least onefeature of the entity to a social media network obtaining module 638.

Referring now to FIG. 7, FIG. 7 illustrates an exemplary implementationof association of the one or more terms of service with a privacy beaconthat is configured to be detected when the at least one feature of theentity is captured in a captured image facilitating module 254. Asillustrated in FIG. 7, the association of the one or more terms ofservice with a privacy beacon that is configured to be detected when theat least one feature of the entity is captured in a captured imagefacilitating module 254 may include one or more sub-logic modules invarious alternative implementations and embodiments. For example, asshown in FIG. 7 (e.g., FIG. 7A), in an embodiment, module 254 mayinclude one or more of association of the one or more terms of servicewith the privacy beacon that is linked to the entity and that isconfigured to be detected when the at least one feature of the entity iscaptured in a captured image facilitating module 702, assignment of theone or more terms of service to the privacy beacon that is configured tobe detected when the at least one feature of the entity is captured in acaptured image facilitating module 708, and linkage of the one or moreterms of service to the privacy beacon that is configured to be detectedwhen the at least one feature of the entity is captured in a capturedimage generating module 710. In an embodiment, module 702 may includeassociation of the one or more terms of service with the privacy beaconthat is linked to the entity and that is configured to be detected by animage capture device when the at least one feature of the entity iscaptured in a captured image facilitating module 704. In an embodiment,module 704 may include association of the one or more terms of servicewith the privacy beacon that is linked to the entity and that isconfigured to be optically detected by an image capture device when theat least one feature of the entity is captured in a captured imagefacilitating module 706.

Referring again to FIG. 7, e.g., FIG. 7B, in an embodiment, module 254may include one or more of placement of the one or more terms of serviceat a particular location configured to allow retrieval of the one ormore terms of service facilitating module 712 and address of theparticular location assignment to the privacy beacon that is configuredto be detected when the at least one feature of the entity is capturedin the captured image facilitating module 714. In an embodiment, module712 may include one or more of placement of the one or more terms ofservice at a particular internet address configured to allow retrievalof the one or more terms of service facilitating module 716, placementof the one or more terms of service in a database record facilitatingmodule 718, and placement of the one or more terms of service at aparticular memory location of a device memory facilitating module 722.In an embodiment, module 718 may include placement of the one or moreterms of service in a database record that is configured to be retrievedthrough use of key data that is at least partially based on dataobtainable from the privacy beacon facilitating module 720.

Referring again to FIG. 7, e.g., FIG. 7C, in an embodiment, module 254may include one or more of one or more terms of service generatingmodule 724 and generated one or more terms of service association withthe privacy beacon that is configured to be detected when the at leastone feature of the entity is captured in the captured image executingmodule 726. In an embodiment, module 724 may include one or more of oneor more terms of service generation that is at least partly based on theat least one feature of the entity performing module 728, one or moreterms of service generation that is at least partly based on at leastone property of the entity performing module 732, one or more terms ofservice generation that is at least partly based on an estimated networth of the entity module 738, and one or more terms of servicegeneration that is at least partly based on one or more existing imagesof the at least one feature of the entity module 740. In an embodiment,module 728 may include one or more terms of service generation that isat least partly based on a category of the at least one feature of theentity performing module 730. In an embodiment, module 732 may includeone or more of one or more terms of service generation that is at leastpartly based on an identity of the entity performing module 734 and oneor more terms of service generation that is at least partly based on anoccupation of the entity performing module 736.

Referring again to FIG. 7, e.g., FIG. 7D, in an embodiment, module 254may include one or more of module 724 and module 726, as previouslydescribed. In an embodiment, module 724 may include one or more of oneor more terms of service generation that is at least partly based on acalculated estimate of a value of an image of the at least one featureof the entity performing module 742 and one or more terms of servicethat specify damages for a use of an image that contains the at leastone feature of the entity generation performing module 744. In anembodiment, module 744 may include one or more terms of service thatspecify an amount of liquidated damages that will be assessed for adistribution of the image that contains the at least one feature of theentity to a social network generation performing module 746. In anembodiment, module 254 may include association of the one or more termsof service with an optically-detectable privacy beacon that isconfigured to be detected in the captured image when the at least onefeature of the entity is captured in the captured image facilitatingmodule 748.

Referring again to FIG. 7, e.g., FIG. 7E, in an embodiment, module 254may include one or more of association of the one or more terms ofservice with a privacy beacon that is configured to emit light in avisible spectrum and configured to be detected in the captured imagewhen the at least one feature of the entity is captured in the capturedimage facilitating module 750 and association of the one or more termsof service with a privacy beacon that is configured to emit light in avisible spectrum and configured to be detected in the captured imagewhen the at least one feature of the entity is captured in the capturedimage facilitating module 756. In an embodiment, module 750 may includeassociation of the one or more terms of service with a privacy beaconthat is configured to emit light in the visible spectrum such that theemitted light is configured to provide data to facilitate acquisition ofthe one or more terms of service and that is configured to be detectedin the captured image when the at least one feature of the entity iscaptured in the captured image facilitating module 752. In anembodiment, module 752 may include association of the one or more termsof service with a privacy beacon that is configured to emit light in thevisible spectrum such that the emitted light is configured to be decodedinto a web address at which the one or more terms of service may beretrieved and that is configured to be detected in the captured imagewhen the at least one feature of the entity is captured in the capturedimage facilitating module 754.

Referring again to FIG. 7, e.g., FIG. 7F, in an embodiment, module 254may include one or more of association of the one or more terms ofservice with the privacy beacon that is configured to be detected at asame time as when the at least one feature of the entity is captured inthe captured image facilitating module 758, instruction to the privacybeacon to issue data that is configured to be used to acquire the one ormore terms of service when the at least one feature of the entity iscaptured in the captured image providing module 762, and instruction tothe privacy beacon to issue data that is the one or more terms ofservice when the at least one feature of the entity is captured in thecaptured image providing module 766. In an embodiment, module 758 mayinclude association of the one or more terms of service with the privacybeacon that is configured to emit a detectable high-frequencylow-penetration signal at the same time as when the at least one featureof the entity is captured in the captured image facilitating module 760.In an embodiment, module 762 may include instruction to the privacybeacon to issue credential data that is configured to be used to acquirethe one or more terms of service when the at least one feature of theentity is captured in the captured image providing module 764.

Referring now to FIG. 8, FIG. 8 illustrates an exemplary implementationof associated one or more terms of service providing to a capture entityassociated with a device that possesses the captured image in responseto an indication that the privacy beacon has been detected module 256.As illustrated in FIG. 8, the associated one or more terms of serviceproviding to a capture entity associated with a device that possessesthe captured image in response to an indication that the privacy beaconhas been detected module 256 may include one or more sub-logic modulesin various alternative implementations and embodiments. For example, asshown in FIG. 8, e.g., FIG. 8A, in an embodiment, module 256 may includeone or more of associated one or more terms of service providing to thecapture entity associated with the device that possesses the capturedimage that includes the privacy beacon in response to an indication thatthe privacy beacon has been detected in the captured image module 802,associated one or more terms of service transmitting to the captureentity associated with the device that possesses the captured image inresponse to the indication that the privacy beacon has been detectedmodule 807, and associated one or more terms of service broadcasting tothe capture entity associated with the device that possesses thecaptured image in response to the indication that the privacy beacon hasbeen detected module 808. In an embodiment, module 802 may includeassociated one or more terms of service that includes a liquidateddamages clause that governs sale of the captured image providing to thecapture entity associated with the device that possesses the capturedimage that includes the privacy beacon in response to the indicationthat the privacy beacon has been detected in the captured image module804. In an embodiment, module 804 may include associated one or moreterms of service that includes a liquidated damages clause thatspecifies five hundred thousand dollars of damages assigned to thecapture entity for sale of the captured image providing to the captureentity associated with the device that possesses the captured image thatincludes the privacy beacon in response to an indication that theprivacy beacon has been detected in the captured image module 806.

Referring again to FIG. 8, e.g., FIG. 8B, in an embodiment, module 256may include associated one or more terms of service providing to aserver device associated with an image capture device that captured thecaptured image in response to an indication that the privacy beacon hasbeen detected module 810. In an embodiment, module 810 may includeassociated one or more terms of service providing to the server deviceassociated with the image capture device that captured the capturedimage and that is configured to determine whether to release thecaptured image in response to an indication that the privacy beacon hasbeen detected module 812. In an embodiment, module 812 may includeassociated one or more terms of service providing to the server deviceassociated with the image capture device that captured the capturedimage and that is configured to determine whether to release thecaptured image at least partly based on the one or more terms of servicein response to an indication that the privacy beacon has been detectedmodule 814.

Referring again to FIG. 8, e.g., FIG. 8C, in an embodiment, module 256may include one or more of indication that the privacy beacon has beendetected receiving module 816 and one or more terms of service providingto the capture entity associated with the device that possesses thecaptured image in response to the indication that the privacy beacon hasbeen detected module 818. In an embodiment, module 816 may include oneor more of indication that the privacy beacon has been detectedreceiving from an image capture device that captured the captured imagemodule 820, indication that the privacy beacon has been detectedreceiving from a server device associated with the image capture devicethat captured the captured image module 822, indication that the privacybeacon has been detected receiving from a privacy beacon monitor devicemodule 824, and indication that the privacy beacon has been detectedreceiving from a device configured to project the privacy beacon module826. In an embodiment, module 818 may include one or more terms ofservice providing to a server device that is configured to determinewhether to release the captured image in response to the indication thatthe privacy beacon has been detected module 828.

Referring again to FIG. 8, e.g., FIG. 8D, in an embodiment, module 256may include one or more of associated one or more terms of serviceproviding to the capture entity associated with a device that possessesthe captured image in response to an indication that the privacy beaconis present in the captured image module 830, associated one or moreterms of service providing to the capture entity associated with thedevice that captured the captured image in response to an indicationthat the privacy beacon is present in the captured image module 832,associated one or more terms of service providing to the capture entityassociated with the device that possesses the captured image in responseto receipt of an identification code of the detected privacy beaconmodule 834, notification that the privacy beacon was detected receivingmodule 838, identity of the detected privacy beacon determining inresponse to the received notification module 840, and one or more termsof service associated with the privacy beacon transmitting to thecapture entity associated with the device that possesses the capturedimage module 842. In an embodiment, module 834 may include associatedone or more terms of service providing to the capture entity associatedwith the device that possesses the captured image in response to receiptof an identification code that uniquely identifies the detected privacybeacon module 836.

Following are a series of flowcharts depicting implementations. For easeof understanding, the flowcharts are organized such that the initialflowcharts present implementations via an example implementation andthereafter the following flowcharts present alternate implementationsand/or expansions of the initial flowchart(s) as either sub-componentoperations or additional component operations building on one or moreearlier-presented flowcharts. Those having skill in the art willappreciate that the style of presentation utilized herein (e.g.,beginning with a presentation of a flowchart(s) presenting an exampleimplementation and thereafter providing additions to and/or furtherdetails in subsequent flowcharts) generally allows for a rapid and easyunderstanding of the various process implementations. In addition, thoseskilled in the art will further appreciate that the style ofpresentation used herein also lends itself well to modular and/orobject-oriented program design paradigms.

Further, in FIG. 9 and in the figures to follow thereafter, variousoperations may be depicted in a box-within-a-box manner. Such depictionsmay indicate that an operation in an internal box may comprise anoptional example embodiment of the operational step illustrated in oneor more external boxes. However, it should be understood that internalbox operations may be viewed as independent operations separate from anyassociated external boxes and may be performed in any sequence withrespect to all other illustrated operations, or may be performedconcurrently. Still further, these operations illustrated in FIGS. 10-12as well as the other operations to be described herein may be performedby at least one of a machine, an article of manufacture, or acomposition of matter.

It is noted that, the term “associated” does not require physicalproximity. A device could be associated with a user if the userpurchased that device, or stores information on that device, or has everlogged in and identified herself to that device. In addition, a devicemay be associated with a user if the user holds the device, carries thedevice, operates the device, or is assigned the device. Similarly, aprivacy beacon may be associated with a terms of service if they areboth associated with the same entity, or if they share some link to eachother, e.g., the privacy beacon may refer to the terms of service, e.g.,directly or indirectly, e.g., the privacy beacon might contain anaddress at which the terms of service may be retrieved.

It is noted that “indicator” and “indication” may, in variousembodiments, refer to many different things, including any of electronicsignals (e.g., pulses between two components), human-understandablesignals (e.g., information being displayed on a screen, or a lighting ofa light, or a playing of a sound), and non-machine related signals(e.g., two people talking, a change in ambient temperature, theoccurrence of an event, whether large scale (e.g., earthquake) orsmall-scale (e.g., the time becomes 4:09 p.m. and 32 seconds)), alone orin any combination.

Referring now to FIG. 9, FIG. 9 shows operation 900, e.g., an exampleoperation of a beacon management device 260 operating in an environment200. In an embodiment, operation 900 may include operation 902 depictingacquiring data that regards at least one feature of an entity that isdesignated for coverage by one or more terms of service. For example,FIG. 2, e.g., FIG. 2B, shows entity data that is related to at least onefeature of an entity that is configured to be assigned for coverage byone or more terms of service obtaining module 252 acquiring (e.g.,obtaining, receiving, calculating, selecting from a list or other datastructure, receiving, retrieving, or receiving information regarding,performing calculations to find out, retrieving data that indicates,receiving notification, receiving information that leads to aninference, whether by human or automated process, or being party to anyaction or transaction that results in informing, inferring, ordeducting, including, but not limited to, circumstances without absolutecertainty, including more-likely-than-not and/or other thresholds) datathat regards (e.g., is related to, includes, identifies, specifies,facilitates, provides an address for, provides credentials for, providesa direction to, provides instructions for generating, etc.) at least onefeature (e.g., a body, a part of a body, a thing carried by a body, athing worn by a body, a thing possessed by a body, where the body is notnecessarily human, living, or animate) of an entity (e.g., a thing,e.g., a person, a rock, a deer, anything that has separate and distinctexistence and objective or conceptual reality) that is designated (e.g.,specified, denominated, named, denoted, alluded to, referred to,selected, marked, labeled, that has been or will be selected, by humanor machine processes, whether automated or input-dependent, or thatincludes such characteristics that allow the feature to be selected, oris identified by other data as selected/designated, or includes datathat informs of a prior designation, etc.) for coverage (e.g., thefeature of the entity is the subject, whether directly or indirectly, oris alluded to, regardless of whether named specifically, namedgenerally, or not named at all) by one or more terms of service (e.g.,one or more terms, definitions, agreements, disclaimers, proclamations,and the like, that are intended to be binding legally upon one or moreparties upon execution of an action, e.g., like viewing a privacybeacon, detecting a privacy beacon, or reading the terms of servicethemselves, where such terms may include user rights andresponsibilities, limits of usage, penalties for misuse, liquidateddamages clauses, general damages clauses, acceptance of risk, assumptionof liability, covenant not to sue, other covenants and agreements, andthe like, a non-limiting example of which is provided below).

Referring again to FIG. 9, operation 900 may include operation 904depicting associating the one or more terms of service with a privacybeacon configured to be detected in an image when the at least onefeature of the entity is captured in the image. For example, FIG. 2,e.g., FIG. 2B, shows association of the one or more terms of servicewith a privacy beacon that is configured to be detected when the atleast one feature of the entity is captured in a captured imagefacilitating module 254 associating (e.g., creating, defining,formalizing, saving, facilitating, or otherwise obtaining or generatinga link, e.g., through data, between) the one or more terms of service(e.g., one or more terms, definitions, agreements, disclaimers,proclamations, and the like, that are intended to be binding legallyupon one or more parties upon execution of an action, e.g., like viewinga privacy beacon, detecting a privacy beacon, or reading the terms ofservice themselves, where such terms may include user rights andresponsibilities, limits of usage, penalties for misuse, liquidateddamages clauses, general damages clauses, acceptance of risk, assumptionof liability, covenant not to sue, other covenants and agreements, andthe like, a non-limiting example of which is provided below) with aprivacy beacon (e.g., a marker detectable by some sensor or otheraction, which may be passive, active, visible or invisible, may operateon the electromagnetic spectrum or in another field, a partial list ofwhich is included below) that is configured to be detected (e.g.,detected in an image here includes detected at the same time an image istaken (e.g., for a beacon that emits nonvisible light, or radio waves,or a thermal signature) that would not be visible in the image, is stillcovered by the “detected in an image”) in an image (e.g., a descriptionof a graphic picture that is a visual representation of something,regardless of whether that something is coherent, nonsensical, abstract,or otherwise) when the at least one feature (e.g., a body, a part of abody, a thing carried by a body, a thing worn by a body, a thingpossessed by a body, where the body is not necessarily human, living, oranimate) of the entity (e.g., a thing, e.g., a person, a rock, a deer,anything that has separate and distinct existence and objective orconceptual reality) is captured (e.g., the image contains arepresentation of, whether through pixel data, vectors, etc.) in theimage (e.g., a description of a graphic picture that is a visualrepresentation of something, regardless of whether that something iscoherent, nonsensical, abstract, or otherwise).

Referring again to FIG. 9, operation 900 may include operation 906depicting providing the terms of service to a capture entity associatedwith a device that captured a captured image that includes the privacybeacon, in response to an indication that the privacy beacon has beendetected. For example, FIG. 2, e.g., FIG. 2B, shows associated one ormore terms of service providing to a capture entity associated with adevice that possesses the captured image in response to an indicationthat the privacy beacon has been detected module 256 determiningproviding (e.g., transmitting, facilitating the transmission of,broadcasting, granting access, providing credentials for, providing anaddress to, giving, unlocking, decrypting, removing protection from,decompressing, etc.) the terms of service (e.g., one or more terms,definitions, agreements, disclaimers, proclamations, and the like, thatare intended to be binding legally upon one or more parties uponexecution of an action, e.g., like viewing a privacy beacon, detecting aprivacy beacon, or reading the terms of service themselves, where suchterms may include user rights and responsibilities, limits of usage,penalties for misuse, liquidated damages clauses, general damagesclauses, acceptance of risk, assumption of liability, covenant not tosue, other covenants and agreements, and the like, a non-limitingexample of which is provided below) to a capture entity (e.g., one ormore devices or other entities that are associated with a capture of anentity, including an image capture device, or one or more devicesassociated with or in communication with the image capture device, e.g.,a smartphone, e.g., a home computer, a remote server, a person that hasthe image capture device, an application running on the image capturedevice or one of the associated devices, e.g., for a specific example,referring to FIG. 2A, image capture device 220 and server device 230 mayeach be capture entities) associated with (e.g., in communication with,is used by a same user as, shares some data with, communicates over asame network, is manufactured by the same manufacturer, has a similarcharacteristic, has a same application resident in memory, has a samecomponent, and also in this context “associated with” may include “is,”for example the “capture entity” may be the device, or it may be aserver in communication with a device, e.g., as an example, the captureentity may be a server 230 associated with the image capture device 220)a device (e.g., any component, including, but not limited to, the imagecapture device 220, which may be a stationary camera, a point-and-shootcamera, a wearable computer with a lens, etc.) that captured (e.g., thatcaptured the image, e.g., through use of an image capturing component,e.g., a lens, or a CCD or CMOS array) a captured image (e.g., adescription of a graphic picture that is a visual representation ofsomething, regardless of whether that something is coherent,nonsensical, abstract, or otherwise, that is in the possession of thedevice, whether because it was taken by the device or transferred to thedevice, or created on the device using an image creation application)that includes (e.g., the privacy beacon is in the image, or was detectedclose-in-time or under same conditions that the image was captured) theprivacy beacon (e.g., a marker detectable by some sensor or otheraction, which may be passive, active, visible or invisible, may operateon the electromagnetic spectrum or in another field, a partial list ofwhich is included below), in response to an indication (e.g., data, or asignal, that informs or is configured to inform, whether directly orindirectly, or whether received internally or externally, whetherreceived, generated, created, etc.) that the privacy beacon (e.g., amarker detectable by some sensor or other action, which may be passive,active, visible or invisible, may operate on the electromagneticspectrum or in another field, a partial list of which is included below)has been detected (e.g., the presence of the privacy beacon has beennoted, which triggered an indicator, which may be as simple as a byte ofdata or a set flag, or a signal or data of any format).

An example terms of service is listed below with the numbered paragraphs1-5. Many other variations of terms of service are known and used inclick-through agreements that are common at the time of filing, and theherein example is intended to be exemplary only and not limiting in anyway.

1. By capturing an image of any part of the user Jules Caesar(hereinafter “Image”), or providing any automation, design, resource,assistance, or other facilitation in the capturing of the Image, youagree that you have captured these Terms of Service and that youacknowledge and agree to them. If you cannot agree to these Terms ofService, you should immediately delete the captured Image. Failure to doso will constitute acceptance of these Terms of Service.

2. The User Jules Caesar owns all of the rights associated with theImage and any representation of any part of Jules Caesar thereof;

3. By capturing the Image, you agree to provide the User Jules Caesarjust compensation for any commercialization of the User's personalityrights that may be captured in the Image.

4. By capturing the Image, you agree to take all reasonable actions totrack the Image and to provide an accounting of all commercializationattempts related to the Image, whether successful or not.

5. By capturing the Image, you accept a Liquidated Damages agreement inwhich unauthorized use of the Image will result in mandatory damages ofat least, but not limited to, $1,000,000.

A privacy beacon may include, but is not limited to, one or more of amarker that reflects light in a visible spectrum, a marker that reflectslight in a nonvisible spectrum, a marker that emits light in a visiblespectrum, a marker that emits light in a nonvisible spectrum, a markerthat emits a radio wave, a marker that, when a particular type ofelectromagnetic wave hits it, emits a particular electromagnetic wave,an RFID tag, a marker that uses near-field communication, a marker thatis in the form of a bar code, a marker that is in the form of a bar codeand painted on a user's head and that reflects light in a nonvisiblespectrum, a marker that uses high frequency low penetration radio waves(e.g., 60 GHz radio waves), a marker that emits a particular thermalsignature, a marker that is worn underneath clothing and is detectableby an x-ray-type detector, a marker that creates a magnetic field, amarker that emits a sonic wave, a marker that emits a sonic wave at afrequency that cannot be heard by humans, a marker that is tattooed to aperson's bicep and is detectable through clothing, a marker that is apart of a user's cellular telephone device, a marker that is broadcastby a part of a user's cellular telephone device, a marker that isbroadcast by a keychain carried by a person, a marker mounted on a dronethat maintains a particular proximity to the person, a marker mounted ineyeglasses, a marker mounted in a hat, a marker mounted in an article ofclothing, the shape of the person's face is registered as the beacon, afeature of a person registered as the beacon, a marker displayed on ascreen, a marker in the form of an LED, a marker embedded on a page, ora book, a string of text or data that serves as a marker, a markerembedded or embossed onto a device, and the like.

FIGS. 10A-10C depict various implementations of operation 902, depictingacquiring data that regards at least one feature of an entity that isdesignated for coverage by one or more terms of service according toembodiments. Referring now to FIG. 10A, operation 902 may includeoperation 1002 depicting acquiring image data that includes an entityimage of the at least one feature of the entity that is designated forcoverage by one or more terms of service. For example, FIG. 6, e.g.,FIG. 6A shows entity image data that includes a photographic depictionof the at least one feature of the entity that is configured to beassigned for coverage by one or more terms of service obtaining module602 acquiring data (e.g., identification data, e.g., “this is a list ofthe parts of the movie star that are to be covered”) that regards atleast one feature (e.g., face, body, private areas) of an entity (e.g.,a person, e.g., a movie star) that is designated for coverage by one ormore terms of service (e.g., a liquidated damages clause forunauthorized use of the image that contains the movie star's face).

Referring again to FIG. 10A, operation 1002 may include operation 1004depicting acquiring image data that includes a facial image of a face ofthe entity that is designated for coverage by one or more terms ofservice. For example, FIG. 6, e.g., FIG. 6A, shows entity image datathat includes a photographic depiction of a face of the entity that isconfigured to be assigned for coverage by one or more terms of serviceobtaining module 604 acquiring image data that includes a facial imageof a face of the entity (e.g., a professional golfer) that is designatedfor coverage by one or more terms of service (e.g., a consequentialdamages clause for unauthorized posting of a picture containing theprofessional golfer's face to a personal blog).

Referring again to FIG. 10A, operation 1004 may include operation 1006depicting acquiring image data that includes multiple facial images fromone or more angles of the face of the entity that is designated forcoverage by one or more terms of service. For example, FIG. 6, e.g.,FIG. 6A, shows entity image data that includes a multiple depictions ofa face of the entity from one or more angles, the face configured to beassigned for coverage by one or more terms of service obtaining module606 acquiring image data that includes multiple facial images from oneor more angles of the face of the entity (e.g., a country music singer)that is designated for coverage by one or more terms of service (e.g., aforeseeable damages clause for posting an image of the singer to asocial network site, e.g., Facebook).

Referring again to FIG. 10A, operation 1002 may include operation 1008depicting acquiring image data that includes an entity image of one ormore body parts of the entity that is designated for coverage by one ormore terms of service. For example, FIG. 6, e.g., FIG. 6A, shows entityimage data that includes a photographic depiction of a body part of theentity that is configured to be assigned for coverage by one or moreterms of service obtaining module 608 acquiring image data that includesan entity image of one or more body parts (e.g., breasts, buttocks,legs) of the entity (e.g., a famous female tennis player) that isdesignated for coverage by one or more terms of service (e.g., a strictliability clause for violations of personality rights of the femaletennis player).

Referring again to FIG. 10A, operation 1008 may include operation 1010depicting acquiring image data that includes an entity image of a fullbody of the entity that is designated for coverage by one or more termsof service. For example, FIG. 6, e.g., FIG. 6A, shows entity image datathat includes a photographic depiction of an entire body of the entitythat is configured to be assigned for coverage by one or more terms ofservice obtaining module 610 acquiring image data that includes anentity image of a full body of the entity (e.g., a prominent politician)that is designated for coverage by one or more terms of service (e.g., acompensatory damages clause for use of an image that contains theprominent politician).

Referring again to FIG. 10A, operation 902 may include operation 1012depicting receiving a three-dimensional model of a head of an entitythat is designated for coverage by one or more terms of service. Forexample, FIG. 6, e.g., FIG. 6A, shows three-dimensional head model dataof a head of the entity that is configured to be assigned for coverageby one or more terms of service obtaining module 612 receiving athree-dimensional model of a head of an entity (e.g., a person who haspaid for protection of personality rights through the privacy beaconsystem described herein) that is designated for coverage by one or moreterms of service (e.g., a recompense of market value of personalityrights clause).

Referring again to FIG. 10A, operation 902 may include operation 1014depicting acquiring data that includes a set of feature coordinates ofthe at least one feature of the entity that is designated for coverageby one or more terms of service. For example, FIG. 6, e.g., FIG. 6A,shows set of feature coordinates that describe at least one feature ofthe entity that is configured to be assigned for coverage by one or moreterms of service obtaining module 614 acquiring data that includes a setof feature coordinates (e.g., a facial characteristic mapping, e.g.,cheekbones, facial structure, etc.) of the at least one feature (e.g., aface) of the entity (e.g., a rock band drummer) that is designated forcoverage by one or more terms of service (e.g., an enforceable penaltyclause).

Referring now to FIG. 10B, operation 902 may include operation 1016depicting acquiring data that regards at least one feature of the entitythat is designated for coverage by one or more terms of service thatgovern one or more images that contain the at least one feature of theentity. For example, FIG. 6, e.g., FIG. 6B, shows entity data that isrelated to at least one feature of the entity that is configured to beassigned for coverage by the one or more terms of service that governone or more images that depict the at least one feature of the entityobtaining module 616 acquiring data that regards at least one feature(e.g., a face and neck) of the entity (e.g., a prominent CEO of a famouscompany) that is designated for coverage by one or more terms of service(e.g., a lost profits damages clause for the sale of) that govern one ormore images that contain the at least one feature (e.g., the face andneck) of the entity (e.g., the prominent CEO of the famous company).

Referring again to FIG. 10B, operation 1016 may include operation 1018depicting acquiring data that regards at least one feature of the entitythat is designated for coverage by one or more terms of service thatdescribe one or more conditions that apply to one or more images thatcontain the at least one feature of the entity. For example, FIG. 6,e.g., FIG. 6B, shows entity data that is related to at least one featureof the entity that is configured to be assigned for coverage by the oneor more terms of service that set one or more conditions that areapplicable to one or more images that depict the at least one feature ofthe entity obtaining module 618 acquiring data that regards at least onefeature (e.g., a face) of the entity (e.g., a professional baseballplayer) that is designated for coverage by one or more terms of servicethat describe one or more conditions (e.g., sale of the image willresult in a $5,000 dollar fine) that apply to one or more images thatcontain the at least one feature (e.g., the face) of the entity (e.g.,the professional baseball player).

Referring again to FIG. 10B, operation 1016 may include operation 1020depicting acquiring data that regards at least one feature of the entitythat is designated for coverage by one or more terms of service thatgovern a use of one or more images that contain the at least one featureof the entity. For example, FIG. 6, e.g., FIG. 6B, shows entity datathat is related to at least one feature of the entity that is configuredto be assigned for coverage by the one or more terms of service thatgovern a use of the one or more images that depict the at least onefeature of the entity obtaining module 620 acquiring data that regardsat least one feature (e.g., a rear end) of the entity (e.g., asupermodel) that is designated for coverage by one or more terms ofservice (e.g., a liquidated damages clause) that govern a use (e.g.,viewing, sale, distribution, e-mailing, posting to a blog, posting to asocial network, manipulating, storing, copying, etc.) of one or moreimages that contain the at least one feature (e.g., the rear end) of theentity (e.g., the supermodel).

Referring again to FIG. 10B, operation 1020 may include operation 1022depicting acquiring data that regards at least one feature of the entitythat is designated for coverage by one or more terms of service thatgovern unauthorized use of one or more covertly-captured images thatcontain the at least one feature of the entity. For example, FIG. 6,e.g., FIG. 6B, shows entity data that is related to at least one featureof the entity that is configured to be assigned for coverage by the oneor more terms of service that govern an unauthorized use of one or moresurreptitiously captured images that depict the at least one feature ofthe entity obtaining module 622 acquiring data that regards at least onefeature (e.g., biceps) of the entity (e.g., a famous bodybuilder) thatis designated for coverage by one or more terms of service (e.g., aconsequential damages clause) that govern unauthorized (e.g., withoutobtaining prior permission) use (e.g., viewing, sale, distribution,e-mailing, posting to a blog, posting to a social network, manipulating,storing, copying, etc.) of one or more covertly-captured (e.g., capturedwithout knowledge by the subject of the image) images that contain theat least one feature (e.g., the biceps) of the entity (e.g., a famousbodybuilder).

Referring again to FIG. 10B, operation 1022 may include operation 1024depicting acquiring data that regards at last one feature of the entitythat is designated for coverage by one or more terms of service thatgovern unauthorized use of one or more covertly-captured images thatcontain the at least one feature of the entity and that were captured bya wearable computer device. For example, FIG. 6, e.g., FIG. 6B, showsentity data that is related to at least one feature of the entity thatis configured to be assigned for coverage by the one or more terms ofservice that govern an unauthorized use of one or more wearable computercaptured surreptitious images that depict the at least one feature ofthe entity obtaining module 624 acquiring data that regards at least onefeature (e.g., a full-body) of the entity (e.g., a famous actress) thatis designated for coverage by one or more terms of service (e.g., aforeseeable damages clause) that govern unauthorized (e.g., withoutobtaining prior permission) use (e.g., viewing, sale, distribution,e-mailing, posting to a blog, posting to a social network, manipulating,storing, copying, etc.) of one or more covertly-captured (e.g., capturedwithout knowledge by the subject of the image) images that contain theat least one feature (e.g., a full body) of the entity (e.g., the famousactress) and that were captured by a wearable computer device (e.g., aGoogle Glass device).

Referring again to FIG. 10B, operation 1020 may include operation 1026depicting acquiring data that regards at least one feature of the entitythat is designated for coverage by one or more terms of service thatgovern a distribution of one or more images that contain the at leastone feature of the entity. For example, FIG. 6, e.g., FIG. 6B, showsentity data that is related to at least one feature of the entity thatis configured to be assigned for coverage by the one or more terms ofservice that govern a distribution of the one or more images that depictthe at least one feature of the entity obtaining module 626 acquiringdata that regards at least one feature (e.g., a face) of the entity(e.g., a professional football quarterback) that is designated forcoverage by one or more terms of service (e.g., a strict liability forpersonality rights violations clause) that govern a distribution (e.g.,a transmitting or broadcasting to one or more entities) of one or moreimages that contain the at least one feature (e.g., the face) of theentity (e.g., the professional football quarterback).

Referring now to FIG. 10C, operation 902 may include operation 1028depicting acquiring a list of at least one feature of the entity that isdesignated for coverage by one or more terms of service. For example,FIG. 6, e.g., FIG. 6C, shows entity data that includes a list of the atleast one feature of an entity that is configured to be assigned forcoverage by one or more terms of service obtaining module 628 acquiringa list of at least one feature (e.g., face) of the entity (e.g., a rockstar) that is designated for coverage by one or more terms of service(e.g., a punitive damages clause for use of the image).

Referring again to FIG. 10C, operation 902 may include operation 1030depicting acquiring a description of at least one feature of the entitythat is designated for coverage by the one or more terms of service. Forexample, FIG. 6, e.g., FIG. 6C, shows entity data that includes adescription of the at least one feature of an entity that is configuredto be assigned for coverage by one or more terms of service obtainingmodule 630 acquiring a description of at least one feature (e.g., a faceand upper body) of the entity (e.g., a female pop music singer) that isdesignated for coverage by the one or more terms of service (e.g., aforeseeable damages clause).

Referring again to FIG. 10C, operation 902 may include operation 1032depicting acquiring data that regards at least one feature of the entitythat is designated for coverage by one or more terms of service that areconfigured to take effect upon capture of an image that contains the atleast one feature of the entity. For example, FIG. 6, e.g., FIG. 6C,shows entity data that is related to at least one feature of the entitythat is configured to be assigned for coverage by one or more terms ofservice that take effect upon acquisition of the at least one feature ofthe entity in an image obtaining module 632 acquiring data that regardsat least one feature (e.g., a face) of the entity (e.g., a professionalhockey player) that is designated for coverage by one or more terms ofservice (e.g., a liquidated damages clause that specifies $4,000 dollarsof damages for posting an image to social media) that are configured totake effect upon capture of an image that contains the at least onefeature (e.g., the face) of the entity (e.g., the professional hockeyplayer).

Referring again to FIG. 10C, operation 902 may include operation 1034depicting acquiring data that regards at least one feature of the entitythat is designated for coverage by one or more terms of service thatspecify a damages for use of an image that contains the at least onefeature of the entity. For example, FIG. 6, e.g., FIG. 6C, shows entitydata that is related to at least one feature of the entity that isconfigured to be assigned for coverage by one or more terms of servicethat specify a damages for use of an image that depicts the at least onefeature of the entity obtaining module 634 acquiring data that regardsat least one feature (e.g., a face) of an entity (e.g., a person workingat a company on a sensitive project) that is designated for coverage byone or more terms of service (e.g., a compensatory damages clause) thatspecify a damages (e.g., $3,000 dollars) for use (e.g., sale,distribution, editing, storing, posting to a network, broadcasting,etc.) of an image that contains the at least one feature (e.g., theface) of the entity (e.g., the person working at the company on thesensitive project).

Referring again to FIG. 10C, operation 1034 may include operation 1036depicting acquiring data that regards at least one feature of the entitythat is designated for coverage by one or more terms of service thatspecify a damages for sale of the image that contains the at least onefeature of the entity. For example, FIG. 6, e.g., FIG. 6C, shows entitydata that is related to at least one feature of the entity that isconfigured to be assigned for coverage by one or more terms of servicethat specify the damages for a sale of the image that depicts the atleast one feature of the entity obtaining module 636 acquiring data thatregards at least one feature (e.g., head and chest) of the entity (e.g.,a prominent local politician) that is designated for coverage by one ormore terms of service (e.g., a liquidated damages clause) that specify adamages (e.g., an amount, e.g., $10,000 dollars) for sale of the imagethat contains the at least one feature (e.g., the head and chest) of theentity (e.g., the prominent local politician).

Referring again to FIG. 10C, operation 1034 may include operation 1038depicting acquiring data that regards at least one feature of an entitythat is designated for coverage by one or more terms of service thatspecify a damages for distribution on a social media network of theimage that contains the at least one feature of the entity. For example,FIG. 6, e.g., FIG. 6C, shows entity data that is related to at least onefeature of the entity that is configured to be assigned for coverage byone or more terms of service that specify the damages for a distributionof the image that depicts the at least one feature of the entity to asocial media network obtaining module 638 acquiring data that regards atleast one feature (e.g., a face) of the entity (e.g., an office worker)that is designated for coverage by one or more terms of service (e.g., aforeseeable damages clause) that specify a damages (e.g., $1,000, plusany foreseeable damages to be calculated post-event) for distribution ona social media network (e.g., Facebook, Twitter, Instagram, Pinterest,including file sharing services, e.g., Picasa, Shutterbox, etc.) of theimage that contains the at least one feature of the entity (e.g., theface of the office worker).

FIGS. 11A-11F depict various implementations of operation 904, depictingassociating the one or more terms of service with a privacy beaconconfigured to be detected in an image when the at least one feature ofthe entity is captured in the image, according to embodiments. Referringnow to FIG. 11A, operation 904 may include operation 1102 depictingassociating the one or more terms of service with the privacy beaconthat is associated with the entity and that is configured to be detectedin an image when the at least one feature of the entity is captured inthe image. For example, FIG. 7, e.g., FIG. 7A, shows association of theone or more terms of service with a privacy beacon that is linked to theentity and that is configured to be detected when the at least onefeature of the entity is captured in a captured image facilitatingmodule 702 associating the one or more terms of service (e.g., aconsequential damages clause) with a privacy beacon (e.g., a marker thatreflects light in a visible spectrum) configured to be detected in animage when the at least one feature (e.g., a face) of the entity (e.g.,a professional basketball player) is captured (e.g., depicted) in theimage (e.g., in the graphical representation of the image data).

Referring again to FIG. 11A, operation 1102 may include operation 1104depicting associating the one or more terms of service with a privacybeacon configured to be detected by an image capture device in an imagewhen the at least one feature of the entity is captured in the image bythe image capture device. For example, FIG. 7, e.g., FIG. 7A, showsassociation of the one or more terms of service with the privacy beaconthat is linked to the entity and that is configured to be detected by animage capture device when the at least one feature of the entity iscaptured in a captured image facilitating module 704 associating the oneor more terms of service (e.g., a liquidated damages clause) with aprivacy beacon (e.g., a marker that emits light in a visible spectrum)configured to be detected by an image capture device (e.g., a wearablecomputer, e.g., a hypothetical Apple-branded wearable computer, e.g.,iGlasses) in an image when the at least one feature of the entity iscaptured in the image by the image capture device (e.g., the wearablecomputer).

Referring again to FIG. 11A, operation 1104 may include operation 1106depicting associating the one or more terms of service with the privacybeacon configured to be optically detected by the image capture devicein the image when the at least one feature of the entity is captured inthe image by the image capture device. For example, FIG. 7, e.g., FIG.7A, shows association of the one or more terms of service with theprivacy beacon that is linked to the entity and that is configured to beoptically detected by an image capture device when the at least onefeature of the entity is captured in a captured image facilitatingmodule 706 associating the one or more terms of service (e.g., aforeseeable damages clause) with the privacy beacon (e.g., a marker thatemits light in a visible spectrum) configured to be optically detected(e.g., detected using optical components, e.g., lenses, mirrors,filters, etc.) by the image capture device (e.g., a wearable computer,e.g., hypothetical Microsoft-branded wearable computer, e.g.,“KinectVision”) in the image when the at least one feature of the entity(e.g., a professional basketball player) is captured in the image by theimage capture device (e.g., the wearable computer, e.g., hypotheticalMicrosoft-branded wearable computer, e.g., “KinectVision”).

Referring again to FIG. 11A, operation 904 may include operation 1108depicting assigning the one or more terms of service to the privacybeacon configured to be detected in an image when the at least onefeature of the entity is captured in the image. For example, FIG. 7,e.g., FIG. 7A, shows assignment of the one or more terms of service tothe privacy beacon that is configured to be detected when the at leastone feature of the entity is captured in a captured image facilitatingmodule 708 assigning the one or more terms of service (e.g., a strictliability clause for personality rights violations) to the privacybeacon (e.g., a marker that is in the form of a bar code) configured tobe detected in an image when the at least one feature (e.g., a rear end)of the entity (e.g., a famous female tennis player) is captured in theimage.

Referring again to FIG. 11A, operation 904 may include operation 1110depicting linking the one or more terms of service to the privacy beaconconfigured to be detected in an image when the at least one feature ofthe entity is captured in the image. For example, FIG. 7, e.g., FIG. 7A,shows linkage of the one or more terms of service to the privacy beaconthat is configured to be detected when the at least one feature of theentity is captured in a captured image generating module 710 linking theone or more terms of service (e.g., a lost profits damages clause forthe sale of the image) to the privacy beacon (e.g., a marker mounted ona drone that maintains a particular proximity to the person) configuredto be detected in an image when the at least one feature (e.g., a face)of the entity (e.g., a famous person) is captured in the image.

Referring now to FIG. 11B, operation 904 may include operation 1112depicting placing the one or more terms of service at a particularlocation configured to allow retrieval of the one or more terms ofservice. For example, FIG. 7, e.g., FIG. 7B, shows placement of the oneor more terms of service at a particular location configured to allowretrieval of the one or more terms of service facilitating module 712placing the one or more terms of service (e.g., an enforceable penaltyclause) at a particular location (e.g., a particular location in memory,a particular record in a database, a particular web address) configuredto allow retrieval of the one or more terms of service (e.g., theenforceable penalty clause).

Referring again to FIG. 11B, operation 904 may include operation 1114depicting assigning an address of the particular location to the privacybeacon configured to be detected in the image when the at least onefeature of the entity is captured in the image. For example, FIG. 7,e.g., FIG. 7B, shows address of the particular location assignment tothe privacy beacon that is configured to be detected when the at leastone feature of the entity is captured in the captured image facilitatingmodule 714 assigning an address of the particular location (e.g., aparticular location in memory, a particular record in a database, aparticular web address) to the privacy beacon (e.g., a marker that is inthe form of a bar code and painted on a user's head and that reflectslight in a visible spectrum) configured to be detected in the image whenthe at least one feature (e.g., forehead) of the entity (e.g., aprofessional singer) is captured in the image.

Referring again to FIG. 11B, operation 1112 may include operation 1116depicting placing the one or more terms of service at a particular website configured to allow retrieval of the one or more terms of service.For example, FIG. 7, e.g., FIG. 7B, shows placement of the one or moreterms of service at a particular internet address configured to allowretrieval of the one or more terms of service facilitating module 716placing the one or more terms of service (e.g., a punitive damagesclause specifying $5,000 dollars in punitive damages for use of theimage) at a particular web site configured to allow retrieval (e.g., bydownloading, e.g., is a publically accessible page) of the one or moreterms of service (e.g., the punitive damages clause specifying $5,000dollars in punitive damages for use of the image).

Referring again to FIG. 11B, operation 1112 may include operation 1118depicting placing the one or more terms of service in a database record.For example, FIG. 7, e.g., FIG. 7B, shows placement of the one or moreterms of service in a database record facilitating module 718 placingthe one or more terms of service (e.g., a compensatory damages clause)in a database record.

Referring again to FIG. 11B, operation 1118 may include operation 1120depicting placing the one or more terms of service in the databaserecord, wherein a database associated with the database record isconfigured to allow retrieval of the one or more terms of service from akey derived from data associated with the privacy beacon. For example,FIG. 7, e.g., FIG. 7B, shows placement of the one or more terms ofservice in a database record that is configured to be retrieved throughuse of key data that is at least partially based on data obtainable fromthe privacy beacon facilitating module 720 placing the one or more termsof service (e.g., a consequential damages for sale of the image clause)in the database record, wherein a database associated with the databaserecord is configured to allow retrieval of the one or more terms ofservice (e.g., the consequential damages for sale of the image clause)from a key derived from data associated with the privacy beacon (e.g., amarker that is worn underneath clothing and is detectable by anx-ray-type detector).

Referring again to FIG. 11B, operation 1112 may include operation 1122depicting placing the one or more terms of service at a particularmemory location configured to allow retrieval of the one or more termsof service from memory. For example, FIG. 7, e.g., FIG. 7B, showsplacement of the one or more terms of service at a particular memorylocation of a device memory facilitating module 722 placing the one ormore terms of service (e.g., an enforceable penalty clause) at aparticular memory location (e.g., within a device or a server)configured to allow retrieval of the one or more terms of service (e.g.,the enforceable penalty clause) from memory.

Referring now to FIG. 11C, operation 904 may include operation 1124depicting generating the one or more terms of service. For example, FIG.7, e.g., FIG. 7C, shows one or more terms of service generating module724 generating (e.g., creating, at least partially) the one or moreterms of service (e.g., a liquidated damages clause that specifies anamount of damages for use of the image at least partially based on a networth of the entity).

Referring again to FIG. 11C, operation 904 may include operation 1126depicting correlating the generated one or more terms of service withthe privacy beacon configured to be detected in an image when the atleast one feature of the entity is captured in the image. For example,FIG. 7, e.g., FIG. 7C, shows generated one or more terms of serviceassociation with the privacy beacon that is configured to be detectedwhen the at least one feature of the entity is captured in the capturedimage executing module 726 correlating the generated one or more termsof service (e.g., the liquidated damages clause that specifies an amountof damages for use of the image at least partially based on a net worthof the entity) with the privacy beacon (e.g., a marker that emits lightin a visible spectrum) configured to be detected in an image when the atleast one feature (e.g., a face) of the entity (e.g., an office workerat a high-security military installation) is captured in the image.

Referring again to FIG. 11C, operation 1124 may include operation 1128depicting generating the one or more terms of service at least partlybased on the feature of the entity. For example, FIG. 7, e.g., FIG. 7C,shows one or more terms of service generation that is at least partlybased on the at least one feature of the entity performing module 728generating the one or more terms of service (e.g., a compensatorydamages clause) at least partly based on the feature (e.g., the moreprivate the feature, the higher the damages percentage, e.g., face,breasts, buttocks, genitalia) of the entity (e.g., a fashion model).

Referring again to FIG. 11C, operation 1128 may include operation 1130depicting generating the one or more terms of service at least partlybased on a type of feature of the entity. For example, FIG. 7, e.g.,FIG. 7C, shows one or more terms of service generation that is at leastpartly based on a category of the at least one feature of the entityperforming module 730 generating the one or more terms of service (e.g.,a consequential damages clause) at least partly based on a type offeature (e.g., is it a private type, e.g., genitals, female breasts, ora public type, e.g., biceps, face, legs) of the entity.

Referring again to FIG. 11C, operation 1124 may include operation 1132depicting generating the one or more terms of service at least partlybased on the entity. For example, FIG. 7, e.g., FIG. 7C, shows one ormore terms of service generation that is at least partly based on atleast one property of the entity performing module 732 generating theone or more terms of service (e.g., a market value of personality rightsas damages for use of the image clause) at least partly based on theentity (e.g., at least partly based on selections that the entity hasmade when setting up the privacy beacon, or how much money the entity ispaying for the service).

Referring again to FIG. 11C, operation 1132 may include operation 1134depicting generating the one or more terms of service at least partlybased on an identity of the entity. For example, FIG. 7, e.g., FIG. 7C,shows one or more terms of service generation that is at least partlybased on an identity of the entity performing module 734 generating theone or more terms of service (e.g., a foreseeable damages clause) atleast partly based on an identity (e.g., the more famous the entity, thelarger the damages clause) of the entity (e.g., a reality televisionstar).

Referring again to FIG. 11C, operation 1132 may include operation 1136depicting generating the one or more terms of service at least partlybased on an occupation of the entity. For example, FIG. 7, e.g., FIG.7C, shows one or more terms of service generation that is at leastpartly based on an occupation of the entity performing module 736generating the one or more terms of service (e.g., a compensatorydamages clause) at least partly based on an occupation of the entity(e.g., a plastic surgeon or an NFL quarterback has more potentialdamages than a regular office worker).

Referring again to FIG. 11C, operation 1124 may include operation 1138depicting generating the one or more terms of service at least partlybased on a net worth of the entity. For example, FIG. 7, e.g., FIG. 7C,shows one or more terms of service generation that is at least partlybased on an estimated net worth of the entity module 738 generating theone or more terms of service (e.g., an enforceable penalty clause with apenalty of $10,000 dollars, which is 1% of the entity's net worth) atleast partly based on a net worth of the entity (e.g., a famous BeverlyHills doctor).

Referring again to FIG. 11C, operation 1124 may include operation 1140depicting generating the one or more terms of service at least partlybased on one or more existing images of the at least one feature of theentity. For example, FIG. 7, e.g., FIG. 7C, shows one or more terms ofservice generation that is at least partly based on one or more existingimages of the at least one feature of the entity module 740 generatingthe one or more terms of service (e.g., a punitive damages clause) atleast partly based on one or more existing images of the at least onefeature (e.g., a face) of the entity (e.g., depending on how much webtraffic other images of the person drive to various gossip sites, whenthe entity is a celebrity).

Referring now to FIG. 11D, operation 1124 may include operation 1142depicting generating the one or more terms of service at least partlybased on an estimated value of an image of the at least one feature ofthe entity. For example, FIG. 7, e.g., FIG. 7D, shows one or more termsof service generation that is at least partly based on a calculatedestimate of a value of an image of the at least one feature of theentity performing module 742 generating the one or more terms of service(e.g., a liquidated damages clause for the sale of an image including amovie star) at least partly based on an estimated value of an image ofthe at least one feature (e.g., a full body) of the entity (e.g., themovie star).

Referring again to FIG. 11D, operation 1124 may include operation 1144depicting generating the one or more terms of service that specifydamages for use of the image that includes the at least one feature ofthe entity. For example, FIG. 7, e.g., FIG. 7D, shows one or more termsof service that specify damages for a use of an image that contains theat least one feature of the entity generation performing module 744generating the one or more terms of service (e.g., a consequentialdamages clause) for use of the image that includes the at least onefeature of the entity (e.g., a face of a country music singer) iscaptured.

Referring again to FIG. 11D, operation 1144 may include operation 1146depicting generating a liquidated damages clause that specifies a setamount of damages for uploading an image of the at least one feature ofthe entity to a social networking site. For example, FIG. 7, e.g., FIG.7D, shows one or more terms of service that specify an amount ofliquidated damages that will be assessed for a distribution of the imagethat contains the at least one feature of the entity to a social networkgeneration performing module 746 generating a liquidated damages clausethat specifies a set amount of damages (e.g., 50,000 dollars) foruploading an image of the at least one feature (e.g., an image thatshows a female celebrity in a bikini) to a social networking site (e.g.,Facebook).

Referring again to FIG. 11D, operation 904 may include operation 1148depicting associating the one or more terms of service with anoptically-detectable privacy beacon configured to be detected in animage when the at least one feature of the entity is captured in theimage. For example, FIG. 7, e.g., FIG. 7D, shows association of the oneor more terms of service with an optically-detectable privacy beaconthat is configured to be detected in the captured image when the atleast one feature of the entity is captured in the captured imagefacilitating module 748 associating the one or more terms of service(e.g., a lost profits damages clause for the sale of the image) with anoptically-detectable privacy beacon (e.g., a marker that is broadcast bya part of a user's cellular telephone device) configured to be detectedin an image when the at least one feature (e.g., a face) of the entity(e.g., a professional ice hockey player) is captured in the image.

Referring now to FIG. 11E, operation 904 may include operation 1150depicting associating the one or more terms of service with the privacybeacon that is configured to emit light in a visible spectrum and thatis configured to be detected in the image when the at least one featureof the entity is captured in the image. For example, FIG. 7, e.g., FIG.7E, shows association of the one or more terms of service with a privacybeacon that is configured to emit light in a visible spectrum andconfigured to be detected in the captured image when the at least onefeature of the entity is captured in the captured image facilitatingmodule 750 associating the one or more terms of service (e.g., aconsequential damages clause) with the privacy beacon that is configuredto emit light in a visible spectrum and that is configured to bedetected in the image when the at least one feature (e.g., a gap-toothedsmile) of the entity (e.g., a famous professional hockey player for theWashington Capitals) is captured in the image.

Referring again to FIG. 11E, operation 1150 may include operation 1152depicting associating the one or more terms of service with the privacybeacon that is configured to emit light in the visible spectrum suchthat emitted light from the privacy beacon is configured to provide datato facilitate acquisition of the one or more terms of service and thatis configured to be detected in the image when the at least one featureof the entity is captured in the image. For example, FIG. 7, e.g., FIG.7E, shows association of the one or more terms of service with a privacybeacon that is configured to emit light in the visible spectrum suchthat the emitted light is configured to provide data to facilitateacquisition of the one or more terms of service and that is configuredto be detected in the captured image when the at least one feature ofthe entity is captured in the captured image facilitating module 752associating the one or more terms of service (e.g., a strict liabilityfor personality rights violation) with the privacy beacon that isconfigured to emit light in the visible spectrum such that emitted lightfrom the privacy beacon is configured to provide data (e.g., a web siteaddress and password access code to the website) to facilitateacquisition of the one or more terms of service (e.g., a strictliability clause for personality rights violation) and that isconfigured to be detected in the image when the at least one feature(e.g., a face) of the entity (e.g., a singer in the Matt & Kim band) iscaptured in the image.

Referring again to FIG. 11E, operation 1152 may include operation 1154depicting associating the one or more terms of service with the privacybeacon that is configured to emit light in the visible spectrum suchthat emitted light from the privacy beacon is configured to be decodedinto a web address at which the one or more terms of service areconfigured to be retrieved. For example, FIG. 7, e.g., FIG. 7E, showsassociation of the one or more terms of service with a privacy beaconthat is configured to emit light in the visible spectrum such that theemitted light is configured to be decoded into a web address at whichthe one or more terms of service may be retrieved and that is configuredto be detected in the captured image when the at least one feature ofthe entity is captured in the captured image facilitating module 754associating the one or more terms of service (e.g., a liquidated damagesclause) with the privacy beacon that is configured to emit light in thevisible spectrum such that emitted light from the privacy beacon isconfigured to be decoded into a web address at which the one or moreterms of service (e.g., a liquidated damages clause) are configured tobe retrieved.

Referring again to FIG. 11E, operation 904 may include operation 1156depicting associating the one or more terms of service with a privacybeacon that is configured to reflect light in a visible spectrum andthat is configured to be detected in the image when the at least onefeature of the entity is captured in the image. For example, FIG. 7,e.g., FIG. 7E, shows association of the one or more terms of servicewith a privacy beacon that is configured to emit light in a visiblespectrum and configured to be detected in the captured image when the atleast one feature of the entity is captured in the captured imagefacilitating module 756 associating the one or more terms of service(e.g., a punitive damages clause) with a privacy beacon that isconfigured to reflect light in a visible spectrum and that is configuredto be detected in the image when the at least one feature of the entity(e.g., a face of a movie star) is captured in the image.

Referring now to FIG. 11F, operation 904 may include operation 1158depicting associating the one or more terms of service with a privacybeacon configured to be detected at a same time that an image of the atleast one feature of the entity is captured. For example, FIG. 7, e.g.,FIG. 7F, shows association of the one or more terms of service with theprivacy beacon that is configured to be detected at a same time as whenthe at least one feature of the entity is captured in the captured imagefacilitating module 758 associating the one or more terms of service(e.g., a consequential damages clause for the distribution of the imageto a social network) with a privacy beacon (e.g., a marker that, when aparticular type of electromagnetic wave hits it, emits a particularelectromagnetic wave, or an RFID tag, or a marker that uses near-fieldcommunication) that is configured to be detected at a same time that animage of the at least one feature (e.g., a face) of the entity (e.g., afamous reality television star) is captured.

Referring again to FIG. 11F, operation 1158 may include operation 1160depicting associating the one or more terms of service with a privacybeacon that is configured to emit a high frequency low penetration radiowave that is detectable at the same time that the image of the at leastone feature of the entity is captured. For example, FIG. 7, e.g., FIG.7F, shows association of the one or more terms of service with theprivacy beacon that is configured to emit a detectable high-frequencylow-penetration signal at the same time as when the at least one featureof the entity is captured in the captured image facilitating module 760associating the one or more terms of service (e.g., a foreseeabledamages clause that specifies damages for a person who emailed the imageto a second person who then posted it to a social network site) with aprivacy beacon that is configured to emit a high frequency lowpenetration radio wave (e.g., a 60 GHz radio wave) that is detectable atthe same time that the image of the at least one feature of the entity(e.g., a face of a professional baseball player) is captured.

Referring again to FIG. 11F, operation 904 may include operation 1162depicting instructing the privacy beacon to facilitate data that isconfigured to be used to obtain the one or more terms of service,wherein the privacy beacon is configured to be detected in the imagewhen the at least one feature of the entity is captured in the image.For example, FIG. 7, e.g., FIG. 7F, shows instruction to the privacybeacon to issue data that is configured to be used to acquire the one ormore terms of service when the at least one feature of the entity iscaptured in the captured image providing module 762 instructing theprivacy beacon (e.g., marker that is broadcast by a keychain carried bya person) to facilitate data (e.g., to provide instructions on how todecrypt or otherwise decode or retrieve data) that is configured to beused to obtain the one or more terms of service (e.g., a compensatorydamages clause), wherein the privacy beacon (e.g., the marker that isbroadcast by a keychain carried by a person) is configured to bedetected in the image when the at least one feature (e.g., a face) ofthe entity (e.g., a soldier at a high-security base installation).

Referring again to FIG. 11F, operation 1162 may include operation 1164depicting instructing the privacy beacon to transmit credential datathat is configured to be used to obtain the one or more terms ofservice, wherein the privacy beacon is configured to be detected in theimage when the at least one feature of the entity is captured in theimage. For example, FIG. 7, e.g., FIG. 7F, shows instruction to theprivacy beacon to issue credential data that is configured to be used toacquire the one or more terms of service when the at least one featureof the entity is captured in the captured image providing module 764instructing the privacy beacon (e.g., a marker that is detectable onlyat a particular range of resolutions of an image) to transmit (e.g., inthe case of a passive privacy beacon, to provide through detection,e.g., like a bar code or other pattern) credential data (e.g.,login/password and key retrieval data) that is configured to be used toobtain the one or more terms of service (e.g., a liquidated damagesclause), wherein the privacy beacon (e.g., the marker that is detectableonly at a particular range of resolutions of an image) is configured tobe detected in the image when the at least one feature of the entity(e.g., a face of a person) is captured in the image.

Referring again to FIG. 11F, operation 904 may include operation 1166depicting instructing the privacy beacon to generate data that is theone or more terms of service, wherein the privacy beacon is configuredto be detected in the image when the at least one feature of the entityis captured in the image. For example, FIG. 7, e.g., FIG. 7F, showsinstruction to the privacy beacon to issue data that is the one or moreterms of service when the at least one feature of the entity is capturedin the captured image providing module 766 instructing the privacybeacon (e.g., a marker that is broadcast by a part of a user's cellulartelephone device) to generate data (e.g., to be broadcast in such ashape that particular data can be derived from the beacon) that is theone or more terms of service (e.g., a strict liability for personalityrights violations clause), wherein the privacy beacon (e.g., the markerthat is broadcast by a program installed on a user's cellular telephonedevice) is configured to be detected in the image when the at least onefeature of the entity (e.g., the face and chest of an office worker at asecretive corporation) is captured in the image.

FIGS. 12A-12D depict various implementations of operation 906, depictingproviding the terms of service to a capture entity associated with adevice that captured a captured image that includes the privacy beacon,in response to an indication that the privacy beacon has been detected,according to embodiments. Referring now to FIG. 12A, operation 906 mayinclude operation 1202 depicting providing the terms of service to thecapture entity associated with the device that captured the capturedimage that includes the privacy beacon, in response to the indicationthat the privacy beacon has been detected in the captured image. Forexample, FIG. 8, e.g., FIG. 8A, shows associated one or more terms ofservice providing to a capture entity associated with a device thatpossesses the captured image that includes the privacy beacon inresponse to an indication that the privacy beacon has been detected inthe captured image module 802 providing (e.g., transmitting) the termsof service (e.g., a consequential damages clause for distribution of theimage) to the capture entity (e.g., a server that receives encryptedimages from a device that captured the image and detected the beacon)associated with the device (e.g., an image capture device, e.g., awearable computer) that captured the captured image that includes theprivacy beacon (e.g., a marker that reflects light in a visiblespectrum), in response to an indication (e.g., data received from thecapture entity, or from another source) that the privacy beacon (e.g.,the marker that reflects light in the visible spectrum) has beendetected in the captured image

Referring again to FIG. 12A, operation 1202 may include operation 1204depicting providing the terms of service that includes a liquidateddamages clause that governs sale of the captured image, said providingto the capture entity associated with an image capture device thatcaptured the captured image that includes the privacy beacon, inresponse to the indication that the privacy beacon has been detected inthe captured image. For example, FIG. 8, e.g., FIG. 8A, shows associatedone or more terms of service that includes a liquidated damages clausethat governs sale of the captured image providing to a capture entityassociated with a device that possesses the captured image that includesthe privacy beacon in response to an indication that the privacy beaconhas been detected in the captured image module 804 providing the termsof service (e.g., a liquidated damages clause) that includes aliquidated damages clause that governs sale of the captured image, saidproviding to the capture entity (e.g., a server that receives encryptedimages from a device that captured the image and detected the beacon)associated with the device (e.g., an image capture device, e.g., awearable computer) associated with (e.g., has a contractual relationshipwith to make decisions regarding the captured image) an image capturedevice (e.g., a still camera that is a traffic camera, or an ATM camera)that captured the captured image that includes the privacy beacon (e.g.,a marker that is tattooed to a person's bicep and is detectable throughclothing), in response to the indication (e.g., the indication is sentby the image capture device, but the service terms are provided to thecapture entity) that the privacy beacon has been detected in thecaptured image.

Referring again to FIG. 12A, operation 1204 may include operation 1206depicting providing the terms of service that includes the liquidateddamages clause that specifies five hundred thousand dollars damages forthe sale of the captured image, said providing to the capture entityassociated with the image capture device that captured the capturedimage that includes the privacy beacon, in response to the indicationthat the privacy beacon has been detected in the captured image. Forexample, FIG. 8, e.g., FIG. 8A, shows associated one or more terms ofservice that includes a liquidated damages clause that specifies fivehundred thousand dollars of damages assigned to the capture entity forsale of the captured image providing to the capture entity associatedwith the device that possesses the captured image that includes theprivacy beacon in response to an indication that the privacy beacon hasbeen detected in the captured image module 806 providing the terms ofservice that includes the liquidated damages clause that specifies fivehundred thousand dollars damages for the sale of the captured image,said providing to the capture entity (e.g., a valuation serverconfigured to receive the captured image and the terms of service and tomake a value judgment regarding whether to allow release of the image)associated with (e.g., receives data from, even if no other relationshipexists) the image capture device (e.g., a wearable computer, e.g., aNokia SMARTglasses) that captured the captured image that includes theprivacy beacon (e.g., a marker mounted in eyeglasses), in response tothe indication that the privacy beacon (e.g., the marker mounted ineyeglasses) has been detected in the captured image.

Referring again to FIG. 12A, operation 906 may include operation 1207depicting transmitting the terms of service to the capture entityassociated with a device that captured a captured image that includesthe privacy beacon, in response to an indication that the privacy beaconhas been detected. For example, FIG. 8, e.g., FIG. 8A, shows associatedone or more terms of service transmitting to the capture entityassociated with the device that possesses the captured image in responseto the indication that the privacy beacon has been detected module 807transmitting the terms of service (e.g., a strict liability forpersonality rights violations clause) to the capture entity (e.g., anadvertisement adding server that evaluates the image and addsadvertisements until a value of the image is greater than or equal to apotential damages specified by the received terms of service) associatedwith a device (e.g., an image capture device, e.g., a wearable computer,e.g., a hypothetical Samsung-branded wearable computer, e.g., a Samsung“Spectacles”) that captured a captured image that includes the privacybeacon (e.g., a marker mounted in a hat), in response to an indication(e.g., data received from the advertisement adding server) that theprivacy beacon (e.g., the marker mounted in the hat) has been detected.

Referring again to FIG. 12A, operation 906 may include operation 1208depicting broadcasting the terms of service to one or more captureentities associated with a device that captured a captured image thatincludes the privacy beacon, in response to an indication that theprivacy beacon has been detected. For example, FIG. 8, e.g., FIG. 8A,shows associated one or more terms of service broadcasting to a captureentity associated with a device that possesses the captured image inresponse to an indication that the privacy beacon has been detectedmodule 808 broadcasting the terms of service (e.g., a compensatorydamages clause) to one or more capture entities (e.g., to an imagecapture device and to an associated server device) associated with adevice (e.g., the image capture device, in the context of this claim“associated with a device” may include “being the device” or “being acomponent or application operating on the device”) that captured acaptured image that includes (e.g., whether visible or invisible, butdetectable by a certain filter) the privacy beacon (e.g., a marker thatemits light in a nonvisible spectrum), in response to an indication thatthe privacy beacon (e.g., the marker that emits light in the nonvisiblespectrum) has been detected.

Referring now to FIG. 12B, operation 906 may include operation 1210depicting providing the terms of service to a server device associatedwith an image capture device that captured a captured image thatincludes the privacy beacon, in response to an indication that theprivacy beacon has been detected. For example, FIG. 8, e.g., FIG. 8A,shows associated one or more terms of service providing to a serverdevice associated with an image capture device that captured thecaptured image in response to an indication that the privacy beacon hasbeen detected module 810 providing the terms of service (e.g., a marketvalue of personality rights clause) to a server device (e.g., that mayissue one or more commands to the image capture device) associated withan image capture device that captured a captured image that includes theprivacy beacon (e.g., a marker that emits a particular thermalsignature), in response to an indication that the privacy beacon hasbeen detected.

Referring again to FIG. 12B, operation 1210 may include operation 1212depicting providing the terms of service to the server device that isassociated with the image capture device and that is configured todetermine whether to allow use of the captured image that includes theprivacy beacon. For example, FIG. 8, e.g., FIG. 8A, shows associated oneor more terms of service providing to the server device associated withthe image capture device that captured the captured image and that isconfigured to determine whether to release the captured image inresponse to an indication that the privacy beacon has been detectedmodule 812 providing the terms of service (e.g., a lost profits damagesclause for the sale of the image) to the server device that isassociated with the image capture device (e.g., a wearable computer) andthat is configured to determine whether to allow use of the capturedimage that includes the privacy beacon (e.g., a marker that is broadcastby a part of a user's smartphone device).

Referring again to FIG. 12B, operation 1212 may include operation 1214depicting providing the terms of service to the server device that isassociated with the image capture device and that is configured todetermine whether to allow use of the captured image that includes theprivacy beacon at least partly based on the one or more terms of serviceassociated with the privacy beacon. For example, FIG. 8, e.g., FIG. 8B,shows associated one or more terms of service providing to the serverdevice associated with the image capture device that captured thecaptured image and that is configured to determine whether to releasethe captured image at least partly based on the one or more terms ofservice in response to an indication that the privacy beacon has beendetected module 814 providing the terms of service (e.g., a strictliability for a personality rights violation clause) to the serverdevice that is associated with the image capture device (e.g., awearable computer, e.g., an Oculon Optoelectronics) and that isconfigured to determine whether to allow use (e.g., sale and/ordistribution) of the captured image that includes the privacy beacon(e.g., the shape of the person's face is registered as the privacybeacon) at least partly based on the one or more terms of service (e.g.,strict liability clauses have a higher likelihood of recovery of damagesand may discourage release) associated with the privacy beacon (e.g.,the shape of the person's face is registered as the beacon, and throughfacial recognition operations, the person is identified and terms ofservice are gathered).

Referring now to FIG. 12C, operation 906 may include operation 1216depicting receiving an indication that the privacy beacon has beendetected. For example, FIG. 8, e.g., FIG. 8C, shows indication that theprivacy beacon has been detected receiving module 816 receiving anindication that the privacy beacon (e.g., a marker mounted on a dronethat maintains a particular proximity to the person) has been detected.

Referring again to FIG. 12C, operation 906 may include operation 1218depicting providing the one or more terms of service to one or morecapture entities associated with the device that captured the capturedimage that includes the privacy beacon. For example, FIG. 8, e.g., FIG.8C, shows one or more terms of service providing to the capture entityassociated with the device that possesses the captured image in responseto the indication that the privacy beacon has been detected module 818providing the one or more terms of service (e.g., a liquidated damagesclause that specifies $50,000 in damages to anyone who uploads the imageto a social networking site without prior authorization) to one or morecapture entities (e.g., a server device that receives a copy of theimage and issues a command to the image capture device regarding whetherto release the image to the user of the image capture device) associatedwith the device (e.g., the wearable computer, e.g., an EyeTap) thatcaptured the captured image that includes the privacy beacon (e.g., themarker mounted on a drone that maintains a particular proximity to theperson).

Referring again to FIG. 12C, operation 1216 may include operation 1220depicting receiving, from an image capture device, an indication thatthe privacy beacon has been detected. For example, FIG. 8, e.g., FIG.8C, shows indication that the privacy beacon has been detected receivingfrom an image capture device that captured the captured image module 820receiving, from an image capture device (e.g., a wearable computer,e.g., Google Glass device), an indication (e.g., data that informs of)that the privacy beacon (e.g., a marker that reflects light in a visiblespectrum) has been detected.

Referring again to FIG. 12C, operation 1216 may include operation 1222depicting receiving, from a server device associated with the imagecapture device and that is configured to determine whether to allow useof the captured image, the indication that the privacy beacon has beendetected. For example, FIG. 8, e.g., FIG. 8C, shows indication that theprivacy beacon has been detected receiving from a server deviceassociated with the image capture device that captured the capturedimage module 822 receiving, from a server device (e.g., a server thatdecides whether the image can be released to the user of the wearablecomputer, e.g., server device 230) associated with the image capturedevice (e.g., the wearable computer, e.g., the Google Glass device) andthat is configured to determine whether to allow use of the capturedimage, the indication that the privacy beacon (e.g., the marker thatreflects light in the visible spectrum) has been detected.

Referring again to FIG. 12C, operation 1216 may include operation 1224depicting receiving, from a privacy beacon monitor device, theindication that the privacy beacon has been detected. For example, FIG.8, e.g., FIG. 8C, shows indication that the privacy beacon has beendetected receiving from a privacy beacon monitor device module 824receiving, from a privacy beacon monitor device (e.g., a centralizeddevice that tracks privacy beacons, e.g., through video surveillance,through communication with the beacon, or through observance of userdata, or other methods), the indication that the privacy beacon (e.g., amarker that is a part of a user's cellular telephone device) has beendetected.

Referring again to FIG. 12C, operation 1216 may include operation 1226depicting receiving, from a device configured to project the privacybeacon, the indication that the privacy beacon has been detected. Forexample, FIG. 8, e.g., FIG. 8C, shows indication that the privacy beaconhas been detected receiving from a device configured to project theprivacy beacon module 826 receiving, from a device configured to project(e.g., a smartphone device) the privacy beacon (e.g., a marker that isbroadcast by a part of a user's cellular telephone device), theindication that the privacy beacon (e.g., the marker that is broadcastby a part of a user's cellular telephone device) has been detected.

Referring again to FIG. 12C, operation 1218 may include operation 1228depicting providing the terms of service to a server device that isconfigured to determine whether to allow use of the captured image. Forexample, FIG. 8, e.g., FIG. 8C, shows one or more terms of serviceproviding to a server device that is configured to determine whether torelease the captured image in response to the indication that theprivacy beacon has been detected module 828 providing the terms ofservice (e.g., a consequential damages clause) to a server device (e.g.,a server device 230 as shown in FIG. 2A) that is configured to determinewhether to allow use of the captured image.

Referring now to FIG. 12D, operation 906 may include operation 1230depicting providing the terms of service to the capture entityassociated with the device that captured the captured image thatincludes the privacy beacon, in response to the indication that thecaptured image contains the privacy beacon. For example, FIG. 8, e.g.,FIG. 8D, shows associated one or more terms of service providing to acapture entity associated with a device that possesses the capturedimage in response to an indication that the privacy beacon is present inthe captured image module 830 providing the terms of service (e.g., acompensatory damages clause) to the capture entity (e.g., a valuationserver configured to receive the captured image and the terms of serviceand to make a value judgment regarding whether to allow release of theimage) associated with the device (e.g., a camera mounted in an ATMmachine) that captured the captured image that includes the privacybeacon (e.g., a marker that emits light), in response to the indication(e.g., from the ATM machine) that the captured image contains theprivacy beacon (e.g., the marker that emits light).

Referring again to FIG. 12D, operation 906 may include operation 1232depicting providing the terms of service to the device that captured thecaptured image that includes the privacy beacon, in response to theindication that the captured image contains the privacy beacon. Forexample, FIG. 8, e.g., FIG. 8D, shows associated one or more terms ofservice providing to the capture entity associated with the device thatcaptured the captured image in response to an indication that theprivacy beacon is present in the captured image module 832 providing theterms of service (e.g., a market value of the personality rights thatwere violated recompense clause) to the device (e.g., a wearablecomputer device, e.g., a hypothetical Apple-branded wearable computer,e.g., Apple “iGlasses”) that captured the captured image that includesthe privacy beacon (e.g., a marker that is tattooed to a person's bicepand is detectable through clothing), in response to the indication(e.g., from a central Apple-branded server that monitors Apple-brandeddevices) that the captured image contains the privacy beacon (e.g., themarker that is tattooed to a person's bicep and is detectable throughclothing).

Referring again to FIG. 12D, operation 906 may include operation 1234depicting providing the terms of service to one or more capture entitiesassociated with the device that captured the captured image thatincludes the privacy beacon, in response to receipt of an identificationcode of a privacy beacon. For example, FIG. 8, e.g., FIG. 8D, showsassociated one or more terms of service providing to the capture entityassociated with the device that possesses the captured image in responseto receipt of an identification code of the detected privacy beaconmodule 834 providing the terms of service to one or more captureentities (e.g., an advertisement adding server that evaluates the imageand adds advertisements until a value of the image is greater than orequal to a potential damages specified by the received terms of service)associated with the device (e.g., a wearable computer device, e.g., ahypothetical Microsoft-branded wearable computer, e.g., Microsoft“Kinect Vision”) that captured the captured image that includes theprivacy beacon, in response to receipt of an identification code of aprivacy beacon (e.g., the image capture device transmits a code that wasread from the beacon that identifies the beacon, e.g., “Jules Caesar'sprivacy beacon).

Referring again to FIG. 12D, operation 1234 may include operation 1236depicting providing the terms of service to the one or more captureentities associated with the device that captured the captured imagethat includes the privacy beacon, in response to receipt of theidentification code that uniquely identifies the privacy beacon. Forexample, FIG. 8, e.g., FIG. 8D, shows associated one or more terms ofservice providing to the capture entity associated with the device thatpossesses the captured image in response to receipt of an identificationcode that uniquely identifies the detected privacy beacon module 836providing the terms of service to the one or more capture entities(e.g., a server that receives encrypted images from a device thatcaptured the image and detected the beacon) associated with the devicethat captured that captured the captured image that includes the privacybeacon, in response to receipt of an identification code that uniquelyidentifies the privacy beacon (e.g., the image capture device transmitsa code that was read from the beacon that identifies the beacon, e.g.,the privacy beacon of movie star Jack Ward).

Referring again to FIG. 12D, operation 906 may include operation 1238depicting receiving a notification that the privacy beacon was detected.For example, FIG. 8, e.g., FIG. 8D, shows notification that the privacybeacon was detected receiving module 838 receiving a notification (e.g.,from an image capture device that captured the beacon, but has noadditional information other than a beacon was captured) that a privacybeacon (e.g., a marker that reflects light in a visible spectrum) wasdetected.

Referring again to FIG. 12D, operation 906 may include operation 1240depicting determining an identity of the privacy beacon that wasdetected. For example, FIG. 8, e.g., FIG. 8D, shows identity of thedetected privacy beacon determining in response to the receivednotification module 840 determining an identity (e.g., an identificationnumber that can be used to retrieve data regarding the entity associatedwith the beacon) of the privacy beacon (e.g., by contacting a privacybeacon watch server that watches various beacons, or, in the case of anactive beacon, communicating with the beacon directly, or with a devicethat projects the beacon) that was detected.

Referring again to FIG. 12D, operation 906 may include operation 1242depicting transmitting the terms of service associated with the privacybeacon to the capture entity associated with the device that capturedthe captured image. For example, FIG. 8, e.g., FIG. 8D, shows one ormore terms of service associated with the privacy beacon transmitting tothe capture entity associated with the device that possesses thecaptured image module 842 transmitting the terms of service (e.g., aliquidated damages clause) associated with the privacy beacon (e.g., amarker that reflects light in a visible spectrum) to the capture entity(e.g., a valuation server configured to receive the captured image andthe terms of service and to make a value judgment regarding whether toallow release of the image) associated with the device (e.g., a wearablecomputer) that captured the captured image.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software(e.g., a high-level computer program serving as a hardwarespecification), firmware, or virtually any combination thereof, limitedto patentable subject matter under 35 U.S.C. 101. In an embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, limited topatentable subject matter under 35 U.S.C. 101, and that designing thecircuitry and/or writing the code for the software (e.g., a high-levelcomputer program serving as a hardware specification) and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link (e.g., transmitter,receiver, transmission logic, reception logic, etc.), etc.).

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in any Application Data Sheet, are incorporated herein byreference, to the extent not inconsistent herewith.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.).

It will be further understood by those within the art that if a specificnumber of an introduced claim recitation is intended, such an intentwill be explicitly recited in the claim, and in the absence of suchrecitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations).

Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that typically a disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms unless context dictates otherwise. For example, the phrase “Aor B” will be typically understood to include the possibilities of “A”or “B” or “A and B.”

With respect to the appended claims, those skilled in the art willappreciate that recited operations therein may generally be performed inany order. Also, although various operational flows are presented in asequence(s), it should be understood that the various operations may beperformed in other orders than those which are illustrated, or may beperformed concurrently. Examples of such alternate orderings may includeoverlapping, interleaved, interrupted, reordered, incremental,preparatory, supplemental, simultaneous, reverse, or other variantorderings, unless context dictates otherwise. Furthermore, terms like“responsive to,” “related to,” or other past-tense adjectives aregenerally not intended to exclude such variants, unless context dictatesotherwise.

This application may make reference to one or more trademarks, e.g., aword, letter, symbol, or device adopted by one manufacturer or merchantand used to identify and/or distinguish his or her product from those ofothers. Trademark names used herein are set forth in such language thatmakes clear their identity, that distinguishes them from commondescriptive nouns, that have fixed and definite meanings, or, in many ifnot all cases, are accompanied by other specific identification usingterms not covered by trademark. In addition, trademark names used hereinhave meanings that are well-known and defined in the literature, or donot refer to products or compounds for which knowledge of one or moretrade secrets is required in order to divine their meaning. Alltrademarks referenced in this application are the property of theirrespective owners, and the appearance of one or more trademarks in thisapplication does not diminish or otherwise adversely affect the validityof the one or more trademarks. All trademarks, registered orunregistered, that appear in this application are assumed to include aproper trademark symbol, e.g., the circle R or bracketed capitalization(e.g., [trademark name]), even when such trademark symbol does notexplicitly appear next to the trademark. To the extent a trademark isused in a descriptive manner to refer to a product or process, thattrademark should be interpreted to represent the corresponding productor process as of the date of the filing of this patent application.

Throughout this application, the terms “in an embodiment,” ‘in oneembodiment,” “in an embodiment,” “in several embodiments,” “in at leastone embodiment,” “in various embodiments,” and the like, may be used.Each of these terms, and all such similar terms should be construed as“in at least one embodiment, and possibly but not necessarily allembodiments,” unless explicitly stated otherwise. Specifically, unlessexplicitly stated otherwise, the intent of phrases like these is toprovide non-exclusive and non-limiting examples of implementations ofthe invention. The mere statement that one, some, or may embodimentsinclude one or more things or have one or more features, does not implythat all embodiments include one or more things or have one or morefeatures, but also does not imply that such embodiments must exist. Itis a mere indicator of an example and should not be interpretedotherwise, unless explicitly stated as such.

Those skilled in the art will appreciate that the foregoing specificexemplary processes and/or devices and/or technologies arerepresentative of more general processes and/or devices and/ortechnologies taught elsewhere herein, such as in the claims filedherewith and/or elsewhere in the present application.

What is claimed is:
 1. A system comprising: a memory bearing one or more executable instructions; and a processor operably coupled to the memory, the processor programmed by the one or more executable instructions to perform operations including at least: acquiring an image including a representation of at least one feature of an entity; detecting a privacy beacon in the image that includes the representation of the at least one feature of the entity; obtaining one or more terms of usage broadcast from the privacy beacon; obfuscating the representation of the at least one feature of the entity in response to detecting the privacy beacon in the image; providing the one or more terms of usage for user acceptance, the one or more terms of usage being automatically adjusted based at least partly on a popularity of the entity and a type of the at least one feature of the entity: and releasing obfuscation of the image including the representation of the at least one feature of the entity upon user acceptance of the one or more terms of usage.
 2. A system comprising: circuitry configured for acquiring an image including a representation of at least one feature of an entity that has been obfuscated; circuitry configured for detecting identifier metadata associated with the image that includes the representation of the at least one feature of the entity; circuitry configured for providing one or more terms of usage for user acceptance based on the identifier metadata, the one or more terms of usage being automatically adjusted based at least partly on a popularity of the entity and a type of the at least one feature of the entity; and circuitry configured for releasing obfuscation of the image including the representation of the at least one feature of the entity upon user acceptance of the one or more terms of usage.
 3. A method implemented by at least one computer processor programmed by one or more machine instructions, the method comprising: acquiring an image including a representation of at least one feature of an entity; detecting a privacy beacon in the image that includes the representation of the at least one feature of the entity; obtaining one or more terms of usage broadcast from the privacy beacon; obfuscating the representation of the at least one feature of the entity in response to detecting the privacy beacon; providing the one or more terms of usage for user acceptance, the one or more terms of usage being automatically adjusted based at least partly on a popularity of the entity and a type of the at least one feature of the entity: and releasing obfuscation of the image including the representation of the at least one feature of the entity upon user acceptance of the one or more terms of usage.
 4. The method of claim 3, further comprising: obtaining the one or more terms of usage that set one or more conditions applicable to the image.
 5. The method of claim 3, further comprising: obtaining the one or more terms of usage that specify one or more damages.
 6. The method of claim 3, further comprising: assigning the one or more terms of usage to the privacy beacon.
 7. The method of claim 3, further comprising: linking the one or more terms of usage with the privacy beacon.
 8. The method of claim 3, further comprising: assigning an address of the one or more terms of usage to the privacy beacon.
 9. The method of claim 3, further comprising: associating the one or more terms of usage with the privacy beacon.
 10. The method of claim 3, wherein the detecting the privacy beacon in the image that includes the representation of the at least one feature of the entity comprises: detecting a light privacy beacon in the image that includes the representation of the at least one feature of the entity.
 11. The method of claim 3, further comprising: obtaining the one or more terms of usage that are transmitted.
 12. The method of claim 3, further comprising: obtaining a web address of the one or more terms of usage.
 13. The method of claim 3, further comprising: generating the one or more terms of usage based at least partly on the at least one feature of the entity.
 14. The method of claim 3, further comprising: generating the one or more terms of usage based at least partly on at least one property of the entity.
 15. The method of claim 3, further comprising: generating the one or more terms of usage based at least partly on a specified net worth of the entity.
 16. The method of claim 3, further comprising: generating the one or more terms of usage that specify one or more damages for use of the image the contains the representation of the at least one feature of the entity.
 17. The method of 16, wherein the generating the one or more terms of usage that specify one or more damages for use of the image the contains the representation of the at least one feature of the entity comprises: generating the one or more terms of usage that specify one or more liquidated damages for distribution to a social network of the image the contains the representation of the at least one feature of the entity.
 18. The method of claim 3, further comprising: obtaining the one or more terms of usage that include a liquidated damages provision.
 19. The method of claim 3, wherein the acquiring an image including a representation of at least one feature of an entity comprises: acquiring at an image capture device an image including a representation of at least one feature of an entity.
 20. The method of claim 3, wherein the acquiring an image including a representation of at least one feature of an entity comprises: acquiring at a server an image including a representation of at least one feature of an entity.
 21. The method of claim 3, further comprising: monitoring for the privacy beacon.
 22. The method of claim 3, further comprising: determining an identity of the privacy beacon.
 23. The method of claim 3, further comprising: performing image recognition with respect to the image to recognize the at least one feature of the entity.
 24. The method of claim 3, further comprising: obtaining as metadata the one or more terms of usage.
 25. The method of claim 3, further comprising: confirming an identity of the entity based at least partly on a combination of recognition of the at least one feature of the entity and metadata.
 26. The method of claim 3, further comprising: acquiring multiple images of the at least one feature of the entity at one or more different angles to facilitate recognition of the at least one feature of the entity.
 27. The method of claim 26, further comprising: identifying the at least one feature of the entity in the image based at least partly on image recognition performed using the multiple images of the at least one feature of the entity.
 28. The method of claim 27, further comprising: generating at least a portion of the one or more terms of usage based at least partly on identification of the at least one feature of the entity in the image.
 29. The method of claim 28, wherein the generating at least a portion of the one or more terms of usage based at least partly on identification of the at least one feature of the entity in the image comprises: generating at least a portion of the one or more terms of usage based at least partly on identification of the at least one feature of the entity in the image and based at least partly on a determined popularity of the entity.
 30. The method of claim of 3, wherein the detecting the privacy beacon in the image that includes the representation of the at least one feature of the entity comprises: optically detecting the privacy beacon in the image that includes the representation of the at least one feature of the entity.
 31. The method of claim 3, wherein the obfuscating the representation of the at least one feature of the entity in response to detecting the privacy beacon comprises: obfuscating the representation of the at least one feature of the entity in response to detecting the privacy beacon and in response to a determination of an absence of a preexisting relationship.
 32. The method of claim 3, wherein the detecting the privacy beacon in the image that includes the representation of the at least one feature of the entity comprises: detecting at least one of the following types of the privacy beacon in the image: metadata, beacon, active, passive, visible, invisible, electromagnetic, thermal, reflective, RFID, near-field-communication (NFC), bar code, magnetic, broadcast, shape, feature, string of text or data, embedded, clothing integrated, or mobile phone integrated.
 33. The method of claim 3, wherein the obfuscating the representation of the at least one feature of the entity in response to detecting the privacy beacon comprises: encrypting the representation of the at least one feature of the entity in response to detecting the privacy beacon.
 34. The method of claim 3, wherein the releasing obfuscation of the image including the representation of the at least one feature of the entity upon user acceptance of the one or more terms of usage comprises: releasing obfuscation of the image for one or more of the following operations: display, access, transmit, post to social networking site, store, share, manipulate, save, or edit. 